The last statement basically means that in case we rely on Equals(..) method we could calculate hash based only on the last name and the result will still be the same:
The inclusion of your comparison class (or more specifically the AsEnumerable call you needed to use to get it to work) meant that the sorting logic went from being based on the database server to being on the database client (your application).
Alternatively, you can write an empty comparer class that implements IEqualityComparer, and then pick the corresponding quick-fix from the Alt+Enter menu:
lakin ben yalnızca otomatik olarak gökçe ve 0 ın tekrarlanmamasını buttona basmış olduğumda kendiliğinden olarak silinsin isterim fareyle seçmek istemiyorum bunun bâtınin bir şifre varmıdır
Name: Bu özelliği kullanarak başka kontrollerde de başüstüneğu üzere Harf kısmında kullanacağımız adı belirliyoruz. Varsayılan olarak listBox1 , listBox2 .. şeklinde bırakılabileceği gibi kendimiz isteğimize görede bir isim verebiliriz.
örnek olarak form1’bile textboxa eklenen metnin butona basıldığında form2 deki textboxa eklenmesi bağırsakin;
Coming soon: Throughout 2024 we will be phasing out GitHub Issues kakım the feedback mechanism for content and replacing it with a new feedback system. For more information see: .
If you look at the definition of Distinct there is only one generic type parameter involved (and hamiş one TCollection used for input and output collections and one TComparison for the comparer).
You have discovered an unfortunate edge case in the generic method type inference algorithm. We have:
operating on different types of classes, even complex types including sub-objects or nested lists. And derece only on simple classes comprising only C# IEqualityComparer Kullanımı primitive type properties.
If there are no fields/properties in your type or you do not select any of them, ReSharper, depending on your settings, throws new NotImplementedException(), returns default value, or puts code that will derece compile in the body of the generated methods. You yaşama configure the settings on the Code Editing
So I'm not 100% clear why you C# IEqualityComparer nerelerde kullanılıyor need the extra comparer. Just the single comparer should be sufficient.
The main use of C# IEqualityComparer Temel Özellikleri ve Kullanımı this interface is you hayat write a single implementation of IEqualityComparer which several classes gönül then use, removing the need to rewrite the C# IEqualityComparer nerelerde kullanılıyor comparison logic for every class.
PS. I don't think any custom Equals methods work with entity framework directly on the database side (I think C# IEqualityComparer Temel Özellikleri ve Kullanımı you know this because you do AsEnumerable) but this is a much simpler method to do a simple Equals for the general case.