Product Features

NDepend is a .NET tool that provides deep insight into code bases. The tool empowers developers, architects and executives to make intelligent decisions on projects. The community name it the "Swiss Army Knife" for .NET programmers.

Easily Manage Large Projects

Most companies have large systems that work together, often in mysterious ways. NDepend's in-depth reporting and toolset can help your company enforce its own coding standards and maintain complex projects.

Code Rule and Code Query

Hundreds of default code rules to check against best practices. Support for Code Query over C# LINQ (CQLinq) to easily customize rules and query code.

Powerful Dependency Graph and Matrix

Explore how the code is actually structured and shed light on architectural flaws thanks to the most powerful code dependency graph and dependency matrix available in the tool industry.

Smart Technical Debt Estimation

For each issue, the cost to fix and the severity are estimated through smart and customizable C# formulas. Thus estimations proposed are realistic.

Continuous .NET Code Quality and Security

A unique approach to continuously keep the technical debt under control and reimburse it with time.

Interactive Web Report

Integrate NDepend analysis into your CI / CD pipeline and obtain interactive and detailed web reports to explore progression and prevent code quality degradation.

 

Quality Gates

Fail the build pipeline upon customizable PASS / WARN / FAIL code quality and security criteria.

 

Import Roslyn Analyzers Issues

Gain a 360 view of your .NET code quality by importing your preferred Roslyn Analyzer issues into the NDepend web report and UI. Track these issues alongside NDepend's rules, and see which ones are new, unresolved, and fixed.

Monitor the Health of Your Application

NDepend allows your team to accurately gauge the overall health of your application, no matter how complex it is.

Trend Monitoring

Get Trend Charts about pretty much any code metrics to master the evolution of your application.

Reduce Friction Between Your Developer Teams

NDepend's reporting and analysis helps architects and developers to communicate and reduce confusion.

Code Diff since Baseline

Compare two versions of a code base and its issues set, and browse diff and changes in any way you can think of.

Working with Legacy Code is Now Easier

By mapping out the structure of the project, it is much easier to see how components and dependencies are connected.

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.

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

Enforce Immutability and Purity

At runtime, program’s states are instance and static fields’ values. Controlling how/when/why states are changing is one of the most challenging programming task. This becomes incredibly difficult in multi-threaded environment. This is because potential side-effects due to a state change get too complicated to be understood.

Object-Oriented developers get more and more inspired by the functional programming approach where most states are immutable. An object is immutable if its state doesn’t change once it has been created. A method is pure if its execution doesn’t change any field state. Immutable objects and pure methods are two efficient ways to limit unexpected side-effects.

Through some dedicated CQLinq conditions and rules, NDepend lets assert immutability and purity on your classes and methods. The best place to start with this feature is to look at the list of default CQLinq rules and to read the associated documentation.

Related Links::
C# Immutable Types: Understanding the Attraction
Enforcing Immutability in Multi-Threaded Projects with NDepend
Code Rule : Fields should be marked as ReadOnly when possible
Code Rule : Avoid non-readonly static fields
Code Rule : Avoid static fields with a mutable field type
Code Rule : Structures should be immutable
Code Rule : Property Getters should be immutable