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

NDepend Users Voice

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Consider XAML during analysis

    Converters are seen as "Dead Code", but most of time, they are used as static resources into XAML. Is there a way to compute it ? Most generally, is it possible with static analysis to make some déductions including XAML code ?

    26 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Code Coverage  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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.

    125 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Code Coverage  ·  Flag idea as inappropriate…  ·  Admin →
  3. Support a generic coverage input format (with documentation)

    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.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Code Coverage  ·  Flag idea as inappropriate…  ·  Admin →
  4. Add support for Dotcover excluded code

    NDepend currently doesn't support code excluded from Dotcover test coverage analyses,resulting in discrepant results when Dotcover coverage filters are added. I propose adding support so that NDepend reports the same test coverage as Dotcover when content has been selected for exclusion.

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Code Coverage  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base