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
  1. 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.

    38 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Code Model  ·  Flag idea as inappropriate…  ·  Admin →
  2. Integrate with IoC Framewoks

    Parse IoC Framewoks settings XML files to append on-demand defined dependencies to the NDepend code model.

    80 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    15 comments  ·  Code Model  ·  Flag idea as inappropriate…  ·  Admin →
  3. Parse VB.NET code

    Parse VB.NET code the same way C# code is parsed, to gather the code metrics # Lines of Comment and Source Code Cyclomatic Complexity from VB.NET code bases.

    70 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Code Model  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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

    67 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Code Model  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Code Model  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base