

- #NDEPEND SERIAL KEY LICENSE KEY#
- #NDEPEND SERIAL KEY ARCHIVE#
- #NDEPEND SERIAL KEY CODE#
- #NDEPEND SERIAL KEY PROFESSIONAL#
NDepend’s metrics view ( Metrics > Code Metrics View in the toolbar or Ctrl + M on the keyboard) allows you to view and highlight various metrics within your code base at various levels.įor example, you can analyze the number of lines of comments on a method basis: Viewing which methods reference a variable within a class. You can even select a variable to highlight all of the methods which reference it. The really nice aspect when it comes to a library is viewing which methods touch which variables. This graph can be zoomed and navigated using your mouse to pan the graph and zoom in on individual classes and methods. The Dependency Graph view for a simple library project. From the Visual NDepend user interface, selecting the menu Graph > View Dependency Graph (or by pressing ALT + G on your keyboard) will open the Dependency Graph view. NDepend also makes it incredibly easy to view a graph of how your dependencies are linked and operate together. You can use these queries to define your own custom rules, making the tool extremely flexible. You can run these queries within the Visual NDepend tool by navigating to the Rules > View Editor Panel menu (or by pressing CTRL + R on your keyboard). NET developers to interrogate your code base.įor example, you can get a list of all methods by running a query such as the following: This allows you to use the LINQ syntax familiar to most. One of the most powerful features of NDepend is their CQLinq (Code Query Linq) query tool. In addition to viewing the report as a HTML file, you can also view it within the Visual NDepend window itself, which presents the same information in a slightly different way and provides some further functionality such as a class and assembly browser. Avoid having different types with same nameĬlicking on each of these yields some further details, such as the class where the rule was violated and some further information on what the rule means.There is a lot of information presented here, but the most important thing to do is to investigate any Critical or Violated rules. The generated report summary rendered in my web browser. I loaded up a small project in Visual NDepend and after a couple of seconds of processing a HTML based report was opened in my web browser. The main window of the Visual NDepend tool.įrom here, it was a case of following the very clear GEtting Started with NDepend guide.

As expected, NDepend can also be integrated into your existing Continuous Integration pipelines to perform static analysis upon build, but I haven’t yet jumped into that side of things.īooting up Visual NDepend presents a fairly familiar looking user interface reminiscent of Visual Studio.
#NDEPEND SERIAL KEY ARCHIVE#
Included in the archive was a README file an executable for NDepend’s stand-alone Visual NDepend tool, which is cool - many tools I’ve used before such as ReSharper are just available as extensions for Visual Studio a command line tool for running analysis and an installer for the Visual Studio extension.Īs having a stand-alone tool to do everything with was somewhat of a novelty, I spent most of my time fiddling with it.
#NDEPEND SERIAL KEY LICENSE KEY#
Upon applying the license key I was generously provided to their website, NDepend downloaded a ZIP file containing several files.
#NDEPEND SERIAL KEY PROFESSIONAL#
I was given access to a Professional license for NDepend and took it for a whirl on some of my projects. NET and for other platforms, such as ReSharper, so I was curious to see what NDepend had to offer. I’ve got some prior experience with static analysis tools for both. There are a variety of metrics, graphs and visualizations which can be applied to help give a directed overview of your project’s structure and any potential problems that may arise. NET project to help understand the code structure and provide suggestions on ways to improve your code quality. NET ecosystem most of the time, I’m always interested in trying out new things. As my current day job currently sees me writing C# and using the. I was recently (well, actually it’s more like 6 months ago now at the time of writing… things managed to get away from me!) contacted with an offer to give NDepend a go and see what it can do. A Brief Look At NDepend Fri, Jun 11, 2021
