I prefer to open/select and postion the windows when and how myself.
I often do not need or want to view the default windows opened and it creates a kind of restlessness in the UI.

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.

At this moment it is not intuitive and very hard to analyze Web sites with ndepend will be very nice if I could get site analyzed in few button clicks

It will be very nice if there will be ability to export dependency graph as SVG image rather than PNG, it definitelly will be less in size and as a bonus it will be resizeable without loosing quality

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.

Just an idea

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.

Is NDepend counting if statements as local variables? The number of local variables reported by NDepend is often much higher than what I manually count. In some cases NDepend is reporting 10+ more local variables in addition to the number that are actually declared.

The description of rule Avoid methods with too many parameters says "This rule matches methods with more than 8 parameters.". The source code finds all methods with greater than 6 parameters.

warnif count > 0 from m in JustMyCode.Methods where
m.NbParameters >= 7

Currently when using NDepend with SonarCube all critical rules are mapped to blocker issues and all other to major issues.

Since NDepend 2017 has introduced the same granularity of issue severity as SonarCube has it would make sense to map it using this severity rating instead of using the obsolete critical/none critical rules flag of NDepend.

Drill into a Method to viewing the dependency graph from that point down only.

Many developers use dark (or various others) theme in VS. NDepend should support that and style its windows accordingly.

Instead of a binary critical or not critical flag for rules, it would be nice to have a weighting system for rules (e.g. "each violation of this rule is worth 3, but each violation of this important rule is worth 8").
Then perhaps we could assign a threshold for whether our analysis failed based on point totals, or some percentage formula.

When and how do you plan to integrate nDepend with vNext build in TFS 2015?

It would be great if you can suppress certain items from the analysis result and add a remark to why you suppressed them.

Some warnings might not be applicable to a certain item in the list, but if you cannot suppress them they will always count the item. Only other option is to fully disable the rule, but this might have unwanted consequences (like no warnings in the past).

A feature like: "Accept this violation" would be highly appreciated.

With the second CTP of VS released recently, there should be a NDepend update soon enabling NDepend in VS '15.

Provide sample project which reflects NDepend abilities for newbies

Exclude all compiler generated code from all graphs and queries by default. This is very cumbersome when working with Task, async and await for .Net 4.5+

Support OpenCover XML Files instead of asking to convert those files to dotcover or NCover formats.