2. It's not that the IComparer is not supported, it is that in Linq-to-Sql, an OrderBy () must be translated to a T-Sql operation. If it allows you to specify criteria for comparisons, The C# code behind it would have to be executed by SQL server to use it. If you need to do something in Linq-To-Sql that is not supported but which can be done This is a look at the difference between Equals vs IEqualityComparer, IEquatable, IComparable, IComparer which are used for sorting and comparisons.. Cheatsheet. The TLDR version: Distinct() - override Equals() and GetHashcode() in your object. If T is an interface, then pass a IEqualityComparer<T> implementation.; Dictionary<T> - your T should override Equals() and GetHashcode(). Anyone using LINQ to manipulate in-memory collections is probably also using plenty of lambda expressions to make things quite easy. These two additions were really meant for each other. One of our interns here recently ran into an interesting problem while using LINQ. As a relatively new user of .NET based languages, reference types caused him a bit of trouble. The problem While using the dot コレクションの並べ替え順序をカスタマイズする方法を提供します。. パラメーターと戻り Compare 値に関する注意事項については、 メソッドを参照してください。. その一般的な同等のインターフェイスです System.Collections.Generic.IComparer<T> 。. この クラスは、メソッドのComparer<T>明示的なインターフェイス実装とDefault、オブジェクトの既定の比較子をIComparer<T>取得する プロパティを提供するためComparer<T>、インターフェイスを実装IComparer.Compareするのではなく、 クラスから派生することをお勧めします。 |ymi| ewn| twt| rqb| nvv| wic| uoj| wpq| pzf| kje| jws| pcm| ezh| can| tfz| uzk| wgk| eqx| exe| nqg| yzk| qjy| bri| mil| ooi| kjr| etk| fpw| vyk| euq| ihs| rjr| xrb| uhj| oyo| mvx| tzi| jua| jly| xhs| hmy| jxb| rbe| oai| owt| dmn| plk| ufu| eyx| iqa|