Ndepend

NDepend is a static analysis tool for .NET managed code. The tool supports a large number of code metrics, including smart technical debt estimations produced by a powerful rules engine to check the code base against best software practices. User-defined rules can be written using C# LINQ queries against the code. More than 150 predefined code rules are proposed. Code rules can be checked automatically in Visual Studio or during continuous integration.NDepend also comes with dependency graphs and dependency matrix to explore the code structure. The tool also performs code base snapshots comparison and this way, all results can be checked against a baseline.Important notice before you startNo data goes outside of your server because The NDepend extension does not use an endpoint to do the analysis. The NDepend tool is embedded in the extension and all the results are stored as a build artifacts in your server.Trial activationBefore adding the NDepend task into your build definition, you have to activate first the NDepend license from the NDepend dashboard.ConfigurationPlease refer to this documentation to configure the NDepend extension.Build TaskThe NDepend DevOps extension consists of a build task that analyses code and code coverage data yielded by the build process.The NDepend DevOps hub presents the results which embed the NDepend dashboard and makes data actionable by drilling down into any item through a single click.DashboardThe hub's Dashboard shows a recap of the most relevant data including technical debt estimations, code size, Quality Gates status, rules and issues numbers.A TFS build can be used as a baseline. All dashboard data is then diff-ed since the baseline.Each Dashboard item is clickable to view more.Quality GatesA Quality Gate is a check on a code quality fact that must be enforced before releasing and eventually, before committing to source control. A Quality Gate can be seen as a PASS/FAIL criterion for software quality.A dozen of default Quality Gates are proposed by NDepend related to measures like technical debt amount, code coverage or amount of issues with particular severity. For example a Quality gate can be written to enforce a certain amount of code coverage by tests ratio on code added and refactored since the baseline.A detailed summary of Quality Gates status is available.RulesMore than 150 default code rules are proposed to check against best practices. Support for Code Query over LINQ (CQLinq) to easily write custom rules and query code. CQLinq is used both to

NDepend: .NET Code Analysis Download the Trial and Get Started in Less than 5 Minutes! NDepend 14-Day Free Trial To help us improve our service, what role do you currently fulfill? * Optional: If you would like to get personal assistance during your trial period, please also let us know who you are: We respect your privacy and take protecting it seriously. We will never sell, rent, lease or give away any information you provide to any third party. * required Why NDepend? NDepend is straightforward to install and easy to use. It produces interactive web reports that can be produced from any CI/CD or DevOps technology (Azure DevOps, GitHub Actions...) on any operating system, Windows, Linux or MacOs. It analyzes code written with latests versions of .NET and C#. NDepend can focus on the changes since a baseline snapshot of your code base, enabling you to enhance newly written code before it reaches production. NDepend provides actionable advices written in plain-english about how to improve your code. It integrates with Visual Studio and interacts side-by-side with Rider and VSCode. With a seamless PASS/FAIL Quality Gate approach NDepend offers the required level of flexibility to enforce what really matters for your organization. It is lightning fast and achieves in seconds what other tools actually achieve in minutes or hours ( we promise, give it a try ). It is straightforward to customize and extend because all of its features rely on C# LINQ queries, which are compiled and executed in

And dependencies are connected. Detect Dependency Cycles Get rid of dependency cycles between components to achieve higher code maintainability. Enforce Immutability and Purity NDepend helps maintaining clean side-effects free code to write highly maintainable products. Real-World Proof Integrate with Visual Studio, Azure DevOps, GitHub and any other CI/CD pipeline, super fast and lightweight analysis, NDepend is conceived for real-world programmers. NDepend.API and Power Tools Write your own static analyzer based on NDepend.API, or tweak existing open-sources Power Tools. In-Depth Issues Management Explore the issues-set in a few clicks and focus your effort on what is urgent and important. See how NDepend can change the way your company creates software.Click below to download your 14 day trial Download free trial. Or you can see how to get started with NDepend and explore its in-depth documentation. Get Started *{padding:0;margin:0;overflow:hidden}html,body{background:#000;height:100%}img{position:absolute;width:100%;top:0;bottom:0;margin:auto}"> *{padding:0;margin:0;overflow:hidden}html,body{background:#000;height:100%}img{position:absolute;width:100%;top:0;bottom:0;margin:auto}"> NDepend lets query the code base over LINQ queries thanks to CQLinq. For example the following CQLinq query matches all public methods that have more than 30 lines of code: from m in Application.Methods where m.NbLinesOfCode > 30 && m.IsPublicselect m Around 200 default queries and rules are provided when you create a new NDepend project. They are easy to read and easy to adapt to your need. Writing CQLinq queries and constraints is straightforward both because it is C# LINQ syntax and because NDepend provides a CQLinq editor which supports: code completion / intellisense live compile error description integrated tooltip documentation Also, once the query is compiled, it gets executed immediately and its result is well displayed and is easy to browse: Powerful and elaborated queries and rules can be written with CQLinq, like the following one for example: // UI layer shouldn't use directly DB typeswarnif count > 0// UI layer is made of types using a UI frameworklet uiTypes = Application.Types.UsingAny(Assemblies.WithNameIn( "PresentationFramework", "System.Windows", "System.Windows.Forms", "System.Web"))// You can easily customize this part to define what are DB types.let dbTypes = ThirdParty.Assemblies.WithNameIn("System.Data", "EntityFramework", "NHibernate").ChildTypes() .Except(ThirdParty.Types.WithNameIn("DataSet", "DataTable", "DataRow"))from uiType in uiTypes.UsingAny(dbTypes)let dbTypesUsed = dbTypes.Intersect(uiType.TypesUsed)let dbTypesAndMembersUsed = dbTypesUsed.Union(dbTypesUsed.ChildMembers().UsedBy(uiType))// Per defaut this rule estimates a technical debt// proportional to the coupling between the UI and DB types.let couplingPerUIType = 2 + uiType.Methods.UsingAny(dbTypesUsed).Count() + dbTypesAndMembersUsed.Count()select new { uiType, dbTypesAndMembersUsed, Debt = (4 * couplingPerUIType).ToMinutes().ToDebt(), Severity = Severity.Major}//// This rule is more a *sample rule to adapt to your need*,// than a rigid rule you should abide by. It shows how to// define code layers in a rule and how to be warned about // layers dependencies violations.//// This rule first defines the UI layer and the DB framework // layer. Second it checks if any UI layer type is using // directly any DB framework layer type.//// • The **DB framework layer** is defined as