I've moved to Visual Studio 2015. I use NCrunch for checking code coverage, which I also upgraded.
The main difference that I noticed was that NCrunch now also includes coverage auto-properties, which wasn't the case with Visual Studio 2013
Is this issue known and how do I fix it?
Remco NCrunch Developer
#7691
03 Sep 2015 10:30 UTC
Hi, thanks for posting.
NCrunch uses the compiler's debug output to determine lines of code. It has no real 'knowledge' of the code itself - rather it interprets the output of the compiler and marks out physical lines where the debugging information exists.
Most likely the change you've observed is caused by the introduced of VS 2015's new C# Compiler, Roslyn. It would seem that Roslyn is now emitting debug data for auto properties - which is something that the previous C# compiler didn't do.
I'm afraid that from the side of NCrunch, there is nothing here to 'fix', in the sense that as long as code has debug data available, it can be tracked and represented as a physical line of code.
Is this behaviour causing problems for you somehow?
NCrunch uses the compiler's debug output to determine lines of code. It has no real 'knowledge' of the code itself - rather it interprets the output of the compiler and marks out physical lines where the debugging information exists.
Most likely the change you've observed is caused by the introduced of VS 2015's new C# Compiler, Roslyn. It would seem that Roslyn is now emitting debug data for auto properties - which is something that the previous C# compiler didn't do.
I'm afraid that from the side of NCrunch, there is nothing here to 'fix', in the sense that as long as code has debug data available, it can be tracked and represented as a physical line of code.
Is this behaviour causing problems for you somehow?
Post a reply
Log in to reply.