I toyed with writing an extension method, also with inheriting from IList and implementing my own Sort() method bey well kakım casting to a List but none of these seemed overly elegant.
But far more importantly, if you are accepting an IList birli a parameter you'd better be careful, because IList and List do not behave the same way. Despite the similarity in name, and despite sharing an interface
If someone passes you an Array or a List, your code will work fine if you check the flag every time and have a fallback... But really; who does that?
It's more nuanced than that. If you are returning an IList as part of the public interface to your library, you leave yourself interesting options to perhaps make a custom list in the future.
In this specific case since you're essentially talking about a language construct, not a custom one it generally won't matter, but say for example that you found List didn't support something you needed.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Most app-level code (i.e. the everyday code that ou write for your application) should probably focus on the generic versions; however there is also a lot of infrastructure code around that must use reflection.
In VS2008, when I click on the service reference and select "Configure Service Reference", there is an option to choose C# IList Nasıl Kullanılır how the client bile-serializes lists returned from the service.
It really comes down to the kind of functionality you need. I'd suggest using the List class in most cases. IList is best for when you need to make a custom array that C# IList Neden Kullanmalıyız could have some very specific rules that you'd like to encapsulate within a collection so you don't repeat yourself, but still want .NET to recognize it birli a list.
Do the decoupling capacitors act C# IList Nedir birli capacitive load to the opamp which is used to make a virtual gorund?
In this case you could pass in any class which implements C# IList Neden Kullanmalıyız the IList interface. If you used List instead, only a List instance could be passed in.
You accept an Interface bey a parameter C# IList Nedir for a method because that allows the caller to submit different concrete types kakım arguments. Given your example method LogAllChecked, the parameter someClasses could be of various types, and for the person writing
additional advantage is that your code is safe from any changes to concrete class birli you are subscribing to only few of the methods of concrete class and those are the ones that are going to be there as long birli the concrete class inherits from the interface you are using.