Please support NDepend for builds which are running inside (linux) dockerfiles.

We've moved from portable to embedded PDBs for our .NET projects - this means there is no longer a separate PDB file and the PDB information is embedded in the assembly. Please can NDepend support this so that queries using .PDBFound and NbLinesOfCode etc. continue to work?

Please make the setup a bit easier to understand. I am a new user for Ndepend and i spent 30 mins trying to create a dependency graph of a existing project and in the end just gave up!

AWS CodeBuild is our go-to solution for building and testing DotNet Core solutions. This would be similar to Appveyor, but benefit from inheriting the IAM security model and S3 storage of artifacts. CodeBuild also recently added Reports which provide a way to track test metrics over time. Seems like a perfect fit.

NDepend is great but it definitely won't be able to cover all requirements for all customers, so, it'll be much better if we can extend NDepend !
In my organization, we've a lot of rules that share some logic so I need to encapsulate this logic in a single extension method either in a C# dll or a CQLinq query and reuse it anywhere.

We've a strict rule that every public member must be documented via xml comments, we need a way to find pieces of code that violate this rule.

Any plans in the works to create rules that enforce IDesign practices & principles (http://www.idesign.net/)?

I'd like to query for instances of the Select N+1 problem. Where database code is happening within a loop resulting in 'N' database queries for each iteration of the loop where one or two well-designed queries would do.

This could be implemented by searching for any method calls to a sub-typer of IRepository<T> or Repository<T> that occurs within a for, foreach or Enumerable loop.

We need to define a set of dependency rules which violating them generates error at development time, local visual studio build, and build server.

To have a widget or page that summarizes on one view ALL builds/projects with a analysis report for a simplistic view of all metrics available.

I would like to see a match CQLinq code edit behavior with VS's one.
eg., select multiple lines, then 'tab' and 'shift+tab' would shift +/-1 tab those lines.
eg., caret not selecting anything but put on line x, then 'ctrl+c' 'ctrl+v' 'ctrl+d' would copy the entire line (with \r\n included), paste the entire line, duplicate the entireline
eg., double click one word would show all usages of this word

• The usage/look/feel is kind of clunky, with so miscellaneous delays and microadjustments, which make it feel slow.


• Several panels are having a 'not really adapted' display.


• A responsive display and adjustments would be much welcome.


• Adding a smart column adjustment (put the mouse cursor between two column titles, the cursor becomes a left-right double arrow, then double click will make the collumn adjust to minimum width without cutting the largest row) would be much welcome.


• etc

The ndepend tool is for profound users, to make it closer to ordinary people I suggest incorporating some elements of augmented reality (like this https://jasoren.com/logistics/)

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.

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

I've depracated a type in my codebase. I want a CQL rule that says 'from this point, don't use any of these methods'.

This request is in response this this SO question: http://stackoverflow.com/questions/37860292/how-can-i-get-ndepend-to-fail-analysis-if-new-calls-are-used-to-a-deprecated-typ