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

42 results found

  1. I would like to be able to easily remove all default NDepend keyboard shortcuts in VS

    I would like to be able to easily remove all default NDepend keyboard shortcuts in Visual Studio.

    NDepend shortcuts seem to be all based on using the Alt key and set at the Global scope, to they regularly conflict with the keyboard shortcuts on tool windows in VS. An example of this is the Find in Files window - I cant hit Alt+A to click the Find All button because NDepend has globally mapped that to some element search tool that I dont need or want to use.

    There are many NDepend commands and its really tedious to unmap them…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  2. Ignore "Avoid having different types with same name" rule for extension classes

    For static classes that only contain extension methods for a particular type, often the class name is in the format of "[Type]Extensions". These classes are most often transparent to the consuming code, and so the reasoning behind the critical rule "Avoid having different types with same name" need not apply, and certainly should not be critical.

    "Such practice leads confusion and also naming collision in source files that use different types with same name."

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  3. Update .NET Profile Directory Resolution

    When using a .NET Profile, the NuGet packages directory stored in the <Dirs> element of the project is fully resolved to include the username. This poses a problem when committing the ndproj file to source control since the project settings are specific to a developer machine. It would be better to use %userprofile% instead:
    %userprofile%\.nuget\packages

    Even further, would it be best to just store the .NET Profile configuration itself in the ndproj project file instead of the corresponding paths? The resolved paths could possibly be saved in the suo file instead. This would also help resolve issues when there are…

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  4. Do not open all kinds of (tool) windows when/after running analysis

    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.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  5. DebtSettings handling when SettingsFilePath is set

    When storing debt settings in an external .ndsettings file, the settings are still pulled in to the ndproj file when the first scan is run. There should be an option to prevent these settings from being copied into the ndproj file. When managing ndproj files using source control, this would lead to fewer changes since the when the external ndsettings file is changed, it would not impact the ndproj files referencing it.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  6. Remove storage of assembly names from NDepend project file

    When NDepend analysis is run for the first time, it adds a list of framework assemblies to the ndproj file, in the <FrameworkAssemblies> section. There doesn't appear to be a way to prevent this from happening. When managing ndproj files in source control, this could lead to additional updates to the ndproj file whenever references within the projects are added or removed. It would be ideal to have an option to prevent this from happening, with these assemblies always being assessed against the build.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  7. 2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  8. ndepend console should run on .NET Standard for Linux based builders

    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.

    35 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  9. Support for Web Sites (WebForms/MVC)

    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

    62 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  10. Ability to export dependency graph as SVG

    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

    42 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  11. NCrunch Code coverage integration.

    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.

    127 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  12. 41 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  5 comments  ·  Admin →
  13. Create an NDepend.CodeModel.IProperty interface

    This would be especially handy to detect with CQLinq when a property is tagged with an attribute, and also to jump from the getter method to the setter method and vice-versa. So IProperty would have to implement the interface NDepend.CodeModel.IAttributeTarget

    75 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Code Model  ·  Admin →
  14. Reference VS solutions from the NDepend Project > Code to Analyze

    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.

    24 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  15. 7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  16. If Statements Counted as Local Variables?

    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.

    1 vote
    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 →
  17. Description and Code for Avoid methods with too many parameters Do Not Match

    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

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  18. Improve mapping of NDepend issues to Sonarcube

    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.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  19. View graph from selected method

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

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  20. Support for dark theme in Visual Studio

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

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
← Previous 1 3
  • Don't see your idea?

Feedback and Knowledge Base