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.
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.
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.
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.
For each issue, the cost to fix and the severity are estimated through smart and customizable C# formulas. Thus estimations proposed are realistic.
A unique approach to continuously keep the technical debt under control and reimburse it with time.
Integrate NDepend analysis into your CI / CD pipeline and obtain interactive and detailed web reports to explore progression and prevent code quality degradation.
Fail the build pipeline upon customizable PASS / WARN / FAIL code quality and security criteria.
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.
NDepend allows your team to accurately gauge the overall health of your application, no matter how complex it is.
Lines of Code, Cyclomatic Complexity, Coupling, Nesting Depth, Rank, NDepend supports them all (and much more).
Get Trend Charts about pretty much any code metrics to master the evolution of your application.
Import test coverage data, and make the most of it in the NDepend feature-rich context.
NDepend's reporting and analysis helps architects and developers to communicate and reduce confusion.
Spot too complex code at a glance thanks to unique diagramming capabilities.
Compare two versions of a code base and its issues set, and browse diff and changes in any way you can think of.
Be warned of potential build process problems before they end up causing friction and pain.
By mapping out the structure of the project, it is much easier to see how components and dependencies are connected.
Get rid of dependency cycles between components to achieve higher code maintainability.
NDepend helps maintaining clean side-effects free code to write highly maintainable products.
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.
Write your own static analyzer based on NDepend.API, or tweak existing open-sources Power Tools.
Explore the issues-set in a few clicks and focus your effort on what is urgent and important.
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