I’ll have to delve into possibly being able to convert the OpenCover reports to one of the above formats and importing it to NDepend.
What we use instead is OpenCover, a great open source alternative. Like many others out there, I’m sure, we’ve got a tight budget and have been busy with other things to get the business to pay us for one of these tools. I quickly found a button to import this though.īut alas! Of the three supported coverage formats, NCover, DotCover and Visual Studio Coverage I’m not using any. This bit is empty for now which makes sense as I’ve yet to give it any code coverage report to work with and if it could statically figure out what coverage I’ve got without even running the tests now that would be magic. Good question, I went for the recommended dashboard view as I’m trying this out and want to see what it has to offer. I also had to modify the default paths but it was quick and easy. Now obviously, this means you’ll have to choose the Debug/Release folder if doing different build configurations which you’re likely to be doing however if you’re using this in CI you can redirect to the right one and if you’re doing it in Visual Studio it ought to be easy enough to switch to the right one and rebuild when you want to inspect the solution with NDepend.
No worries though, just choose “Add assemblies in folder” and pick your choice from the output folder. We’ve got quite a big code base by now and most of the projects don’t compile individually but congregate into one output folder for the entire application.
Now, this may for you as for me be a bit tricky. However, running the visual studio extension installer wouldn’t work unless I right clicked and ran it as an administrator, no biggie just worth mentioning. It still makes sense to put it there rather than anywhere else so I’m fine with that. I installed it to %programfiles% as per the instruction though you will get prompted with a UAC, which is stated on the web page, it’s just something you need to live with. NDepend simply comes as a zip file which contents you drop in a folder, completely fine and it’s a one line instruction on what you need to do, “unpack and run xxx”. InstallationĪfter writing a few installers myself using both the old fashion visual studio included tools and lately using Wix I can appreciate that the NDepend team didn’t waste time trying to do this. In this blog post I’ll take you through my initial 2-3h user journey in trying out the tool. It uses a Linq based paradigm to build rules around the code metadata it reads from the solution making it incredibly versatile in terms of extending and customizing. Now NDepend is a tool, both command line, stand alone and as an addin to Visual Studio which allows you to do static analysis and reporting on your. I got the chance to try out NDepend, although with everything else, it took me quite some time until I finally got around to picking it up.
0 kommentar(er)
