Why am I getting "Collection was modified; enumeration operation may not execute" when not modifying the enumerated collection? [duplicate]

This question already has answers here: 开发者_运维问答 How to remove elements from a generic list while iterating over it? (28 answers) Closed 9 years ago.

I have two collections of strings: CollectionA is a StringCollection property of an object stored in the system, while CollectionB is a List generated at runtime. CollectionA needs to be updated to match CollectionB if there are any differences. So I devised what I expected to be a simple LINQ method to perform the removal.

var strDifferences = CollectionA.Where(foo => !CollectionB.Contains(foo));
foreach (var strVar in strDifferences) { CollectionA.Remove(strVar); }

But I am getting a "Collection was modified; enumeration operation may not execute" error on strDifferences... even though it is a separate enumerable from the collection being modified! I originally devised this explicitly to evade this error, as my first implementation would produce it (as I was enumerating across CollectionA and just removing when !CollectionB.Contains(str)). Can anyone shed some insight into why this enumeration is failing?

---

The two are not completely separate. Where does not make a separate copy of the collection. It internally keeps a reference to the original collection and fetches elements from it as you request them.

You can solve your problem by adding ToList() to force Where to iterate through the collection immediately.

var strDifferences = CollectionA
    .Where(foo => !CollectionB.Contains(foo))
    .ToList();

---

Where passes back IEnumerable<T> and then you are using that in your foreach (var strVar in strDifferences)

You are then trying to remove it from the collection that created the IEnumerable<T>. You haven't created a new list, it's referencing CollectionA to pull the next item from, so you can't edit CollectionA.

You can do this also:

var strDifferences = CollectionA.Where
  (foo => CollectionB.Contains(foo)).ToList();

CollectionA = strDifferences;
//or instead of reassigning CollectionA
CollectionA.Clear();
CollectionA.AddRange(strDifferences);

Since you are removing the ones that aren't in CollectionB. Just look for the ones that are, create a list and assign that list to the CollectionA variable.

---

Try modifying the first line a bit:

var strDifferences =
    CollectionA.Where(foo => !CollectionB.Contains(foo)).ToList();

I think LINQ is using lazy execution of your query. The call to ToList will force execution of the query prior to enumerating.