Allow to choose a color for a code element on the dependency graph view and by default choose a color for the query targets and another one for the query results.

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 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!

The UI can be overwhelming. I think it would be nice to have different profiles, e.g. for advanced and novice users.

The novice user should have a preset of settings which allow him only to see the basic features... just to create more overview.

Whereas the advanced user doesn't have to remove all the info messages/window.

Currently if code is made using dependency injection NDepend fails to detect cyclic dependencies. Sample code:

public interface Interface1
{
    void Foo();
};

public interface Interface2
{
    void Bar();
};

public class MyClass1 : Interface1
{
    private Interface2 _interface2;
    public MyClass1(Interface2 interface2)
    {
        _interface2 = interface2;
        _interface2.Bar();
    }

    void Interface1.Foo()
    {
    }
}

public class MyClass2 : Interface2
{
    private Interface1 _interface1;
    public MyClass2(Interface1 interface1)
    {
        _interface1 = interface1;
        _interface1.Foo();
    }

    public void Bar()
    {
    }
}

Using SonarQube, I see that they have a rule for flagging code that has been commented-out. Does this exist in NDepend, or could it be added?

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

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

I stumbled upon that properties in the API do not work correctly with managed C++ projects. For example IAssembly.VisualStudioProjectFilePath always returns null in case of a vcxproj or ISourceFile.Language always returns SourceFileLanguage.Other.
This is not about full support for managed C++ but basic things like the ones above would be great if they work when working in a heterogenous environment.

Hi Patrick,
the Font of the text in the Dependency Graph are extremely different in size.

The bigger are huge and the other so tiny to be unreadable.

This makes the graph much less usable
https://i.imgur.com/d5GUtby.png

My suggestion, use the font maximum size to 16px and minimum size to 7 px and use all the available space.

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

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

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.

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

I'd love it if the Visual Studio add-in would highlight the location of the visual studio editor in the various NDepend views - particularly the code metrics tree map. I'd love to see where I am in code as I'm actively editing C# or VB .NET code.

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.

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