NDepend currently doesn't support code excluded from Dotcover test coverage analyses,resulting in discrepant results when Dotcover coverage filters are added. I propose adding support so that NDepend reports the same test coverage as Dotcover when content has been selected for exclusion.

NDepend's method variable count metric considers each exception catch statement to add another variable to the method's variable count. I can understand how those strictly would be considered function variables, but how is this helpful for code quality? Properly handling exceptions should not compete with keeping the method variable count low. Surely it is not bad practice to catch a number of specific exceptions. It seems like bad practice to create a separate wrapper function just to try/catch exceptions in the inner function. How would one refactor this to make it better?

A visual indicator indicates in the VS code editor for each code element (method, field, type, namespace) if it violates one or several rules.

From this visual indicator it is possible to jump to the code rule(s) violated)

The rule status would be updated asynchronously after 2 to 5 seconds (depending on the size of the code base) each time the user types and reach a compilable status.

The aim is to produce in the NDepend report a graph based on a specific CQL query like it is possible in the UI via the 'Export To Graph' command.

Today only the full 'Dependency Graph' is generated in our nightly report.

Example : Generate a graph of dependencies on a specific set of assemblies. Grab this image and integrate it in a live design document.

It would be great to be able to select multiple nodes in the Query Result or the Class Browser.

Right-clicking them would lead to special menus, like:
- Copy as text,
- Export/Append to Matrix/Graph,
- Create code queries like, Who is Using Any of Us, Who is Using All of Us...

It would also be great to be able to drag&drop them to Graph or Matrix.

The idea is to add a major feature of code clones hunting. We have ideas of original, fast yet effective algorithms. Is it something you'd like to have in the context of NDepend?

Would be nice to:

1. Be able to define subgroups with the same name as other top level groups. Example | Code Quality Regression | Custom Group | Code Quality Regression The above example throws an error.
2. Be able to select and copy/move multiple rules to different groups.

If you've got a symbol server or reindexed pdbs that have commands in them to get source from version control systems (or somewhere else for that matter) and you try navigating to a method, the source code is appropriately requested based on the commands in the PDBs.

We would like to have an alert if there is a public method without a method summary on certain namespaces.
Can nDepend help us with that??

THANKS guys!

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

aka "MyMetrics"

Create a new kind of Report for Managers that presents a synthesis of data, like Code Quality ranked from 1 to 10, Code Structure ranked from 1 to 10 ...

Provide an OSS web server that could be developed with NDepend.API to present data through an interactive web site.

Add Color to the Treemap Metric Panel to be able to observe a second metric on the treemap.

Define the first Analysis Result of a Project as a baseline for further Analysis Results (not applicable to Temporary projects)

Actually the code element right clicked is inferred from the method body, type body, namespace body where the right-click occur. Provide a finer inference of the code element right clicked based on symbol names right-clicked (like if a type name in a method signature is right clicked, infer the type instead of the method).