Provide a Jenkins CI plugin to integrate NDepend analysis and gather NDepend code metrics from Jenkins CI.

Being able to filter on attribute property values.

One example is to check categories on Test methods (i.e. the value from [TestCategory("IntegrationTest")]).

Provide a Bamboo plugin to integrate NDepend analysis and gather NDepend code metrics from Bamboo.

Parse IoC Framewoks settings XML files to append on-demand defined dependencies to the NDepend code model.

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

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.

It would be interesting to see how many TODOs we have in code
Or how much we added in the last Sprint

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.

NDepend code model should propose a getter IType[] IMethods.ParametersTypes to be able to write certain code queries and rules, like security related ones.

Just an idea

A lot of .NET people are starting to use AppVeyor a lot, it would be pretty awesome if you could integrate with it.

Allow additional 'custom' metrics to be added to the nDepend dashboard.
For example: Count of "TODO"

aka "MyMetrics"

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.

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 ?

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.

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.