![]() ![]() NDepend extension for Azure DevOps is available in Visual Studio Marketplace and installation is pretty straightforward, just as for any other Azure DevOps extension. Improving and enforcing source code quality with NDepend Azure DevOps extension You can check out available licensing options here: NDepend Licensing Options and compare NDepend Editions here: Compare NDepend Editions. There is a 14-day trial period available for NDepend for Developer and Build Machine licenses, and a 28-day trial period for Azure DevOps/TFS extension. Please note: NDepend is a subscription-based commercial tool and you will need to buy a license in order to be able to use it. Since there are so many use cases and so many possibilities NDepend has to offer I will not be going through all of them, but I will focus on one specific use cases which I was experimenting with: incorporating code quality analysis and enforcing code quality policies with NDepend through Azure DevOps and Visual Studio extensions. Documentation is pretty detailed and extensive which makes it pretty easy to get started and get your hands dirty with the tool. The tool is quite extensive and has a lot of use cases starting from architecture-related functionality like building project and class dependency diagrams to incorporating build quality policies as part of CI/CD pipelines in Azure DevOps and other CI servers. So what is NDepend? It's a static code analysis tool for. I've heard about NDepend many times before and from time to time stumbled upon reviews from other developers, but now the time has come to test it out myself and see what the tool is capable of. NDepend has a long history dating back to 2004 and it has gained quite a lot of popularity in the. Recently I got an opportunity to explore and experiment with a tool called NDepend and I would like to share some of the possibilities this tool provides in this blog post. ![]() Fortunately for us there are many tools in the industry that may help us with this. This is something that's extremely difficult to achieve manually, especially when you have a bigger application with tens of developers working on it. It's equally important to keep the code base maintainable and clean, minimize complexity, dependencies and technical debt, ensure that the new code follows the same quality and design standards as the rest of the code base. ![]() When developing software it's important to focus on fullfilling customer requirements, providing best possible user experience, performance, security, availability and many other -ilities to ensure success of the software you're building, as well as keep your current users loyal and happy about your product.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |