Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

NCrunch Metrics are wrong
PGJohn
#1 Posted : Thursday, September 3, 2015 8:35:49 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 9/3/2015(UTC)
Posts: 1
Location: United Kingdom

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
#2 Posted : Thursday, September 3, 2015 10:30:07 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,144

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
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?
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

YAF | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.026 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download