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

44 results found

  1. List Rules Violations

    In addition to list rules violated, list rules violations in a new dedicated panel. This would be convenient to pinpoint which assembly / which namespace / which class concentrate a lots of violations.

    16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  2. Provide Visual Studio 15 integration

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

    10 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  3. Path

    Improved Path Support: please implement an improvement to Path support such that I can use both relative path + path variables in the ndproj file.

    This is important as I want to be able to:

    • add specific assemblies to the ndproj using a relative path. This means that when I branch, I don't need to update the default value to include the new branch name when using Visual NDepend

    • support two standard arguments used through our build process $(Configuration) and $(Platform)

    Example of what I want to be able to do in he Path References screen (screenshots available on request):

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  4. Support for builds running inside dockerfiles

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

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  6. Support for embedded PDB

    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?

    7 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 →
  7. 7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  8. Add a command line argument to Depend.Console.exe to be able to pass the code coverage files

    When building with TeamCity you can generate dotCover coverage files which would be convenient to be able to pass as parameters to Depend.Console.exe

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  9. 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…)
  10. Support UNC Paths and Shared Drives paths

    Support UNC Paths and Shared Drives paths for files and dirs paths referenced by NDepend Projects

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  11. 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…)
  12. 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…)
  13. 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…)
  14. 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…)
  15. 2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  16. 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…)
  17. 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 →
  18. Add importance weighting to rules for more robust "fails"

    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.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  19. 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…)
  20. Let's the user edit multiple Graphs and multiple Matrix

    Save Graphs and Matrix edition in XML files referenced from the NDepend projects.

    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  ·  Dependency Graph  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base