This post originated from an RSS feed registered with .NET Buzz
by Jeff Key.
Original Post: NCover * 2
Feed Title: Jeff Key
Feed URL: http://www.asp.net/err404.htm?aspxerrorpath=/jkey/Rss.aspx
Feed Description: Topics revolve around .NET and the Windows platform.
I don't recall ever being so happy, confused, sad and uncertain at the same time. Sells has found a new code coverage project for .NET called, you guessed it, NCover.
Happy: I've been waiting for a .NET code coverage tool for a long time.
Confused: As Craig Andera points out in the comments, there is another NCover project on SourceForge, released on the same day. Interestingly, the GDN one is a command-line app and the one on SF appears to be an NAnt task.
Sad: I can't get the command-line version to generate any output. I don't use NAnt at home, so I haven't tried the SF one yet.
Uncertain: I started writing a simple static call coverage app last week. Rather than watching runtime usage, it inspects the IL of all assemblies it's given and documents which classes aren't used, methods that aren't called, etc. Nothing fancy.
If anyone gets any of the NCovers working, feel free to leave a response.
Previous Topic
