Being able to filter on attribute property values.

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

NCrunch is an absolute must have tool, and it does code coverage very well. i'd like to see a way to get NCrunch Code Coverage data into NDepend.

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

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.

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

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

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

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.

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

This would be especially handy to see dependencies between groups of assemblies in the matrix or in the graph. Groups of assemblies could be also useful for grouping code elements in rules or query results.

Lets group boxes in the graph and and sub-graph in boxes.

When using the SuppressMessageAttribute, the suppressed issues are grouped in the query result view. It would be very useful to also see the suppression ‘Justification’. Perhaps add a column so we could group by justification? Thanks.

With custom colors [1], It would be great to sync the ndepend UI colors with those of VS, is case of using this extension. Without it, the last VS color is "coming back" at every launch.

[1] https://marketplace.visualstudio.com/items?itemName=VisualStudioPlatformTeam.VisualStudio2017ColorThemeEditor

Sometimes queries need to be modified by us, but sometimes those queries are very generic and should be there for ALL Projects, for example today with Support they helped me to create a query to avoid a warning with JustMyCode.

If there were a central repository of Queries, then Ndepend would be able to connect to it (Nuget style) and the user would be able to select if they want to update or not the local queries. (Queries would need some versioning)

While supporting various code coverage output formats is helpful and is ideal from an ease-of-use standpoint, there will always be that one more coverage tool.

If instead you provide a documented xml(json, whatever) format, then one can transform the output of a coverage tool to that format without waiting for support for the format to be added to NDepend, or the coverage tool can even directly support an NDepend output option.

I want to store and reload the layout of a graph. When I analyse existing code, the layout needs to be adjusted manually to define clusters. It would be good if those adjustements can be stored not just as graphics, but as model layout. Alternatively adding special elements to support building group might be useful.

Why should we have to download anything to update the software? Provide us a button to click to perform an Update.

There is a Description in each violation but there could be a further link to your website explaining more and giving some code examples e.g. code before the change and suggested change so it complies.

Also the suggested Fixes are quite brief. While an experienced developer could know what to do, less experienced developer would have difficulties.

More real life small examples would educate, help and guide developers faster to make a better code.

And yes, these examples could be for each violations :)

Property accessors usually only use 1 field. If they are used to compute the LOCOM metric then the result can be very misleading.