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
96 results found
-
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 -
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 -
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 ?
28 votes -
2 votes
-
NDepend should not consider exception catch() parameters as method variables
NDepend's method variable count metric considers each exception catch statement to add another variable to the method's variable count. I can understand how those strictly would be considered function variables, but how is this helpful for code quality? Properly handling exceptions should not compete with keeping the method variable count low. Surely it is not bad practice to catch a number of specific exceptions. It seems like bad practice to create a separate wrapper function just to try/catch exceptions in the inner function. How would one refactor this to make it better?
2 votes -
Better support for QHD displays in Visual Studio Plugin
When running ndepend on QHD display (e.g. 3200*1600), some screens have too small controls/content. E.g. Dependency Matrix, Dashboard
3 votes -
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 -
Show rules violated by code elements in VS code editor and update status live
A visual indicator indicates in the VS code editor for each code element (method, field, type, namespace) if it violates one or several rules.
From this visual indicator it is possible to jump to the code rule(s) violated)
The rule status would be updated asynchronously after 2 to 5 seconds (depending on the size of the code base) each time the user types and reach a compilable status.
0 votes -
Generate a graph from a custom CQL query
The aim is to produce in the NDepend report a graph based on a specific CQL query like it is possible in the UI via the 'Export To Graph' command.
Today only the full 'Dependency Graph' is generated in our nightly report.Example : Generate a graph of dependencies on a specific set of assemblies. Grab this image and integrate it in a live design document.
11 votes -
Multiple Nodes Selection in Query Result or Class Browser
It would be great to be able to select multiple nodes in the Query Result or the Class Browser.
Right-clicking them would lead to special menus, like:
- Copy as text,
- Export/Append to Matrix/Graph,
- Create code queries like, Who is Using Any of Us, Who is Using All of Us...It would also be great to be able to drag&drop them to Graph or Matrix.
3 votes -
Allow Search of string literals.
It would be extremely handy (especially when working with legacy code) to be able to search string literals. This comes in handy especially when working with code that does reflection, some types of IOC registration, and code that may pass on certain types of information as string literals.
12 votes -
A 'Hound' like product for .Net projects
I recently ran across a new project called 'Hound' http://robots.thoughtbot.com/introducing-hound that help developers fight the smaller code quality issues by commenting on github pull requests. This made me think of NDepend as a Service and would be a nice way to integrate NDepend into my workflow - by simply commenting on offending lines of a pull request a team could start to have an automated way of having the team fix things that might otherwise be missed. I really like how hound talks about removing the 'human' from some of the littler issues.
I could see this starting out as…
1 vote -
Customize pre-defined nDepend dashboard (non-chart)
Allow to change pre-defined or define new custom metrics (non chart) similar to '#Types', 'Third-Party Usage', 'Method Complexity', etc. on the dashboard so it is clear decrease or increase of a specific metric (comparisons with a baseline snapshot). This is useful especially when the increase is very small and might be difficult to follow on a chart.
Be able to remove some of the predefined stats from the dashboard similar to what is available with the predefined charts.
32 votes -
Queries explorer enhancements.
Would be nice to:
- Be able to define subgroups with the same name as other top level groups. Example | Code Quality Regression | Custom Group | Code Quality Regression The above example throws an error.
- Be able to select and copy/move multiple rules to different groups.
2 votes -
Provide a plugin to integrate NDepend with atlassian Bamboo
Provide a Bamboo plugin to integrate NDepend analysis and gather NDepend code metrics from Bamboo.
110 votes -
Code clone hunting
The idea is to add a major feature of code clones hunting. We have ideas of original, fast yet effective algorithms. Is it something you'd like to have in the context of NDepend?
14 votes -
Navigation honours metadata in reindexed PDBs
If you've got a symbol server or reindexed pdbs that have commands in them to get source from version control systems (or somewhere else for that matter) and you try navigating to a method, the source code is appropriately requested based on the commands in the PDBs.
11 votes -
Allow custom definitions similar to JustMyCode
The JustMyCode definition is really nice and useful. I'd like to have a similar concept for other things, e.g. JustMyBusinessLogic or JustMyDatabaseLayer. Today I need to create different NDepend projects and adapt the JustMyCode definition for each of them.
45 votes -
Being able to read attribute property values
Being able to filter on attribute property values.
One example is to check categories on Test methods (i.e. the value from [TestCategory("IntegrationTest")]).
135 votes -
Is there a possibility to see if there is method summary available?
We would like to have an alert if there is a public method without a method summary on certain namespaces.
Can nDepend help us with that??THANKS guys!
6 votes
- Don't see your idea?