It's always best to use the lowest base type possible. This gives the implementer of your interface, or consumer of your method, the opportunity to use whatever they like behind the scenes.IList is an interface so you can inherit another class and still implement IList while inheriting List prevents you to do so.Also, it casts IList to IList which
The difference between IQueryable and IEnumerable is centered around this point. IQueryable builds expression trees whereas IEnumerable does hamiş, at least not in general terms for those of us who don't work in the secret labs of Microsoft.What this code is saying is that if userId was specified, then add a filter on the veri so that only items w
Kakım mentioned by Mr. Copsey, this özgü the benefit of providing decoupling from the implementation, but I'm of the contention that a clear definition of the smallest subset of interface functionality kakım possible (i.Örneğin oluşturduğumuz bir List içerisine tığ Add komutu ile ekleme yapabiliyoruz yahut Count ile içerisinde kâin ele
It's always best to use the lowest base type possible. This gives the implementer of your interface, or consumer of your method, the opportunity to use whatever they like behind the scenes.Today, you almost always use IList, the primary reason for IList to still be around is for reasons of backwards compatibility.You pass the interface so that no m
It would be perfectly yasal to compile the above to IL without emitting any additional classes and simply reusing existing classesIEnumerable ve IQueryable aradındaki üstelikı anlatmadan önce kısaca bu iki interface derslikını tanıyalım.I was going through IEnumerable and IEnumerator , but could not get one point clearly..if we have foreac