NDepend User Voice
Welcome to the NDepend User Voice page. Let us know what you would like to see in future versions of NDepend. This site is for suggestions and ideas. If you need to report a bug, please send us an email at support@ndepend.com
We look forward to hearing from you!
Thanks – Patrick Smacchia
NDepend Team
-
Provide a Jenkins CI plugin
Provide a Jenkins CI plugin to integrate NDepend analysis and gather NDepend code metrics from Jenkins CI.
147 votes -
Being able to read attribute property values
Being able to filter on attribute property values.
One example is to check categories on Test methods (i.e. the value from [TestCategory("IntegrationTest")]).
135 votes -
Provide a plugin to integrate NDepend with atlassian Bamboo
Provide a Bamboo plugin to integrate NDepend analysis and gather NDepend code metrics from Bamboo.
107 votes -
Integrate with IoC Framewoks
Parse IoC Framewoks settings XML files to append on-demand defined dependencies to the NDepend code model.
86 votes -
76 votes
-
Create an NDepend.CodeModel.IProperty interface
This would be especially handy to detect with CQLinq when a property is tagged with an attribute, and also to jump from the getter method to the setter method and vice-versa. So IProperty would have to implement the interface NDepend.CodeModel.IAttributeTarget
72 votes -
Parse VB.NET code
Parse VB.NET code the same way C# code is parsed, to gather the code metrics # Lines of Comment and Source Code Cyclomatic Complexity from VB.NET code bases.
70 votes -
Rules: Provide possibility to search for code comments. Example: Count "TODO" or Count "HACK"
It would be interesting to see how many TODOs we have in code
Or how much we added in the last Sprint66 votes -
Allow custom definitions similar to JustMyCode
The JustMyCode definition is really nice and useful. I'd like to have a similar concept for other things, e.g. JustMyBusinessLogic or JustMyDatabaseLayer. Today I need to create different NDepend projects and adapt the JustMyCode definition for each of them.
45 votes -
I see you have integration for Reflector, is there any interest in providing a dotPeek integration as well?
Just an idea
41 votes -
Be able to query methods parameters types
NDepend code model should propose a getter IType[] IMethods.ParametersTypes to be able to write certain code queries and rules, like security related ones.
41 votes -
Ability to analyze NuGet packages
There are currently project types for analyzing a project/solution and for analyzing a folder full of assemblies.
Much of my work lately has been in creating smaller, standalone "framework" sorts of packages on an internal NuGet feed that different applications can consume. There isn't "a master project" that has all of these packages working together; instead it's different combinations of the packages.
I'd like to be able to analyze all of these packages in a single report without having to either manually download them all or create a "fake" project just for the sake of referencing them.
One way to…
39 votes -
AppVeyor Integration
A lot of .NET people are starting to use AppVeyor a lot, it would be pretty awesome if you could integrate with it.
38 votes -
ndepend console should run on .NET Standard for Linux based builders
We are beginning to move towards linux based builders using a .NET Core environment for our .NET Core projects that are not dependent on windows. Because NDepend is a part of our build process, we cannot run any analysis at build times on the projects that have moved in that direction.
Make NDepend.Console .NET Core compliant so that it can run on these Linux builders and restore full analysis capability to out builds.
35 votes -
Halstead metrics in NDepend
I would like to strongly advise the implementation in NDepend, of Halstead metrics that are already available in CppDepend. I frequently used the CppDepend maintainability index and other economic metrics to justify important and strategic refactoring.
I utilize other tools to measure the scope and monetary values of changes in C# code base. Yet, I apply other formulas, but without the same accuracy. To apply different formulas may induce contradictions that I must explain, which transform my project meetings almost to courses in software engineering metric and indicators.
To hold the same metrics on both CppDepend and NDepend provides uniformity…
35 votes -
Customize pre-defined nDepend dashboard (non-chart)
Allow to change pre-defined or define new custom metrics (non chart) similar to '#Types', 'Third-Party Usage', 'Method Complexity', etc. on the dashboard so it is clear decrease or increase of a specific metric (comparisons with a baseline snapshot). This is useful especially when the increase is very small and might be difficult to follow on a chart.
Be able to remove some of the predefined stats from the dashboard similar to what is available with the predefined charts.
32 votes -
Allow additional 'custom' metrics on the nDepend dashboard
Allow additional 'custom' metrics to be added to the nDepend dashboard.
For example: Count of "TODO"aka "MyMetrics"
31 votes -
Consider XAML during analysis
Converters are seen as "Dead Code", but most of time, they are used as static resources into XAML. Is there a way to compute it ? Most generally, is it possible with static analysis to make some déductions including XAML code ?
28 votes -
Add code churn metrics from source control
It would be extraordinarily useful to include code churn metrics from source control. This would be an extremely helpful metric to help decide what parts of the codebase a team should look to start cutting down complexity, dependencies, and other issues.
I use code churn when it's available to help identify modules, classes, or methods that we should focus on. Items with high churn indicate they're getting touched a lot, which often indicates brittle sections of the codebase.
Since this is totally dependent on each particular source control system, it would make sense to start with only one or two…
27 votes -
Reference VS solutions from the NDepend Project > Code to Analyze
In addition to references assemblies to analyze from NDepend project, make possible to reference also one or several VS solutions. Assemblies could then be resolved from a defined VS solutions configuration. Also a filter by name system would be handy to filter for example tests assemblies from the VS solutions.
24 votes
- Don't see your idea?