I am experiencing weird issues during Visual Studio 2015 Community debugging a 32-bit C# application (C# 6, .NET 4.5.2) on Windows 8.1 x64.
If I do a couple of Edit and Continue iterations (i.e. break execution, change something, continue), after a while I will get a weird NullReferenceException thrown for a field which cannot possibly be null. When I then hover over the this instance for the "offending" object, it turns out that there are multiple fields with the same name inside that object (and for each pair of fields, one of them with the expected value, the other one null). This happened a couple of times already, and wasn't fixed after installing VS2015 Update 1 either.
It seems like a Roslyn issue to me, like it has problems recompiling after Edit and Continue. Is this a known issue that has workarounds?
