icollection

I try to do static class, add to icollection but i got some issues i cant seem to overcome. that is how i get so i can pass a ICollection in the method? cause T is that say it can not be resolved. and then i wonder is there a way to do AddRange on icollection? i was thinking of something like this but maby i am way out of my mind with it? public static ICollection<T> add(this IEnumerable<T> list) { ICollection<T> collection = null; return collection.AddRange(list); } No, ICollection<T> doesn't have an AddRange method - and even if it did, you'd be trying to dereference null which will throw a

I'm trying to understand the point of the syncroot in ICollection. Why not just lock the collection? lock(myCollection) { //do stuff to myCollection } vs lock(myCollection.SyncRoot) { //do stuff to myCollection } Typically, if thread safety is a serious concern, I would avoid either of these options. A far better option is typically to maintain your own private variable , and lock on it in all methods where it's required - including the entire public API that accesses the collection. The real danger is that, by locking on a type that's exposed or could be exposed to the outside world, you

What is the difference between IEnumerable and IEnumerable<T> ? I've seen many framework classes implementing both these interfaces, therefore I would like to know what advantages one get by implementing both? Please have a look how they've been defined: public interface IEnumerable { [DispId(-4)] IEnumerator GetEnumerator(); } public interface IEnumerable<T> : IEnumerable { IEnumerator<T> GetEnumerator(); } As we see, IEnumerable<T> derives from IEnumerable , that means whatever IEnumerable has, IEnumerable<T> inherits, then why do we implement both instead of just IEnumerable<T> ? Is

I've extracted the setting names and their respective values out of a configuration file into an ordered dictionary. The dictionary contains keys and values which are of the ICollection class. I want to bind that data and display it in a DataGridView. I've tried copying the strings to arrays and displaying those arrays, but when I ran the program the columns were blank and it did not seem to be binded at all. I've also attempted to set the DataGridView source directly to one the ordered dictionary collections (keys or values), but that also did not result in anything I wanted; the columns were

I only watched a few webcasts before I went head first in to designing a few Entity Framework applications. I really didn't read that much documentation and I feel like I am suffering for it now. I have been using List<T> in my classes, and it has worked great. Now I have read some documentation and it states that I should have been using ICollection<T> . I changed to this, and it didn't even cause a model context change. Is this because both List<T> and ICollection<T> inherit IEnumerable<T> , and that is what is actually required for EF? However, if this is the case, why doesn't the EF

I see this a lot in tutorials, with navigation properties as ICollection<T> . Is this a mandatory requirement for Entity Framework? Can I use IEnumerable ? What's the main purpose of using ICollection instead of IEnumerable or even List<T> ? Usually what you choose will depend on which methods you need access to. In general - IEnumerable<> (MSDN: http://msdn.microsoft.com/en-us/library/system.collections.ienumerable.aspx ) for a list of objects that only needs to be iterated through, ICollection<> (MSDN: http://msdn.microsoft.com/en-us/library/92t2ye13.aspx ) for a list of objects that needs