I have never used NDepend so obviously I was very curious. In my daily job at Dell we obviously make an extensive use of static code analysis tools as part of our build pipelines. We also run them a bunch of times on our machine, but that’s not a mandatory step.
These tools are getting exceptionally good and they provide an enormous value on every codebase. Period.
They can easily assist spotting nasty issues that could even get past test pipelines. Moreover, some cases they can give very good refactoring suggestions, helping out cleaning the code.
So, going back to NDepend, it’s one of the best .NET analysis tools on the market. Check out the website for the list of features, the list is definitely impressive.
The installation was pretty straightforward, no issues at all. Just follow the steps shown in the Getting Started section.
I installed the VS2019 integration and then loaded one of the projects I’m working on these days. It contains 4 class libraries and the relative test projects. Launched the NDepend analysis, filtered out the tests (with the “-test” filter) and waited few seconds for the process to complete.
Now, I have to admit that big dashboards scare me. I’m not particularly good at reading stats and making immediately sense out of them. Usually takes me some time to get used to the results format.
But in this case almost everything was clear…also the results were quite nice and that definitely cheered me up 😀
All in all, I’m quite happy with NDepend . After less than 30 minutes I was already updating my codebase and committing changes based on the suggestions.
Of course I just scratched the surface, there are tons of features that I need to explore. I haven’t even used the Coverage tool yet.
I think I’m definitely going to add it to my daily routine. I’ll blog more in the next days as soon as I get more “intimate” with it 🙂