Skip to content

NDepend User Voice

Welcome to the NDepend User Voice page. Let us know what you would like to see in future versions of NDepend. This site is for suggestions and ideas. If you need to report a bug, please send us an email at support@ndepend.com

We look forward to hearing from you!

Thanks – Patrick Smacchia
NDepend Team

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

94 results found

  1. Provide a UI to list and manage History Analysis Results

    In the NDepend Project Properties > Analysis > Baseline for Comparison > History Analysis Results, the user can choose where History Analysis Results are stored and the frequency of storage.These results can then be used as baseline.

    It might happen that some History Analysis Results are lacking some important data, like coverage data or some specific source code data, because at analysis time this info was not available.

    When such result is chosen as baseline, this has an important impact on issues computed and on the technical debt estimated. For now the user can remove concerned History Analysis Result by…

    17 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Add support for dependency cycles detection for the code using dependency injection

    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()
        {
        }
    }
    
    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Add support for .NET Core packaged application analysis

    When .NET Core assemblies and applications are built and packaged using dotnet CLI (e.g., "dotnet pack") the build output isn't a folder full of assemblies the way it was in classic .NET - it's a NuGet .nupkg file with the assembly (or full application) inside.

    In the case of applications, this includes not only the entry point (e.g., "MyApplication.exe") but also any dependent assemblies required to make the app run. That even means all of the base framework assemblies ("System.Collections.dlll") - there is no reference to any installed .NET Framework. The dotnet CLI and runtime take care of that and…

    13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. User forum for discussion / self-help

    If there is a user forum to ask other users for help, search discussions, and discuss usage, my bad as I have not found it.

    I would like to be able to openly discuss and search discussions with NDepend and NDepend users to find out how others are using the product. How tos, workarounds, find out what it does not do before loosing a lot of time coming to the same conclusion.

    I believe an open forum provide more that what support can (not criticism intended).

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Allow to define colors on dependency graphs

    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.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. TFS 2015 Update 3 VSO Build Code Coverage Integration

    Integrate NDepend into TFS 2015 Update 3 VSO Build technology, specifically with historical trending code coverage analysis in mind.

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Have ability to create rule that compares trend metrics between builds

    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

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Advice on splitting applications

    I have come across several examples in my development career where the code has become monolithic and shared amongst multiple applications. For example, a project that I worked on recently had two websites - one for internal admin and one for external and the code is not well-segmented into different assemblies.

    It would be nice to be able to select two application projects and get an output for items used separately and shared. You can do this by querying but a simple method would be useful.

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Highlight the IDE's currently selected method, class, and assembly in NDepend views

    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.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Halstead metrics in NDepend

    I would like to strongly advise the implementation in NDepend, of Halstead metrics that are already available in CppDepend. I frequently used the CppDepend maintainability index and other economic metrics to justify important and strategic refactoring.

    I utilize other tools to measure the scope and monetary values of changes in C# code base. Yet, I apply other formulas, but without the same accuracy. To apply different formulas may induce contradictions that I must explain, which transform my project meetings almost to courses in software engineering metric and indicators.

    To hold the same metrics on both CppDepend and NDepend provides uniformity…

    38 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Code Metrics  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Basic support for managed C++

    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.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Code Model  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Allow adding comments to disabled rules

    It would be great if you can add a comment to a disabled rule. For some libraries we disable some of the rules and it would be great if we can put a remark why we disable a certain check. It would also be okay if we have to put it in the rule definition.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Create profiles for different levels of experience

    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.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Enable search in Options

    Just like in Visual Studio 2015, it would be nice to have a possibility to search in the options.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Provide auto-code fixes for simple issues

    I use ReSharper a lot when coding, especially for refactoring. With the new Roslyn compiler, a bunch of these refactoring shortcuts also ship with Visual Studio and now can also be custom made ( https://www.youtube.com/watch?v=Ip6wrpYFHhE )

    I found myself having to 'seal' 70 classes and I was looking for a NDepend function that does it automatically. Couldn't find it. So my idea is to provide auto-refactoring helpers for easy code fixes ( like sealing a class ).

    17 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Ability to analyze NuGet packages

    There are currently project types for analyzing a project/solution and for analyzing a folder full of assemblies.

    Much of my work lately has been in creating smaller, standalone "framework" sorts of packages on an internal NuGet feed that different applications can consume. There isn't "a master project" that has all of these packages working together; instead it's different combinations of the packages.

    I'd like to be able to analyze all of these packages in a single report without having to either manually download them all or create a "fake" project just for the sake of referencing them.

    One way to…

    39 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Be able to query methods parameters types

    NDepend code model should propose a getter IType[] IMethods.ParametersTypes to be able to write certain code queries and rules, like security related ones.

    42 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Code Model  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Add code churn metrics from source control

    It would be extraordinarily useful to include code churn metrics from source control. This would be an extremely helpful metric to help decide what parts of the codebase a team should look to start cutting down complexity, dependencies, and other issues.

    I use code churn when it's available to help identify modules, classes, or methods that we should focus on. Items with high churn indicate they're getting touched a lot, which often indicates brittle sections of the codebase.

    Since this is totally dependent on each particular source control system, it would make sense to start with only one or two…

    27 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. AppVeyor Integration

    A lot of .NET people are starting to use AppVeyor a lot, it would be pretty awesome if you could integrate with it.

    38 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Flag commented-out code.

    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?

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Feedback and Knowledge Base