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
-
Examples & Documentation and Guiding Developers
There is a Description in each violation but there could be a further link to your website explaining more and giving some code examples e.g. code before the change and suggested change so it complies.
Also the suggested Fixes are quite brief. While an experienced developer could know what to do, less experienced developer would have difficulties.
More real life small examples would educate, help and guide developers faster to make a better code.
And yes, these examples could be for each violations :)
2 votes -
LCOM Metric Should Not Include Property Accessors
Property accessors usually only use 1 field. If they are used to compute the LOCOM metric then the result can be very misleading.
1 vote -
Find empty catch blocks
Empty catch blocks are a serious maintainability/reliability issue, as is doing too much in a catch block. Would be great to have an easy way to locate/count all the places where catch blocks have no executable code in them, and/or get a line of code count in all catch blocks across an application.
15 votes -
Be able to run R# "refactor"-commands based a NDepend query result
Query code base in order to modify.
ReSharper is best in facilitating refactoring.
NDepend is best in facilitating code analysis and locating pieces of code.Solution: integrate the ReSharper and NDepend in any suitable way.
1 vote -
Add a minimal deployment option for build agents
Although admittedly NDepend isn't a huge product, it would be helpful if there was a secondary deployment option which was just NDepend.Console.exe and its dependencies. No GUI tools, power tools, integration extensions etc. Just the absolute basics so that you can easy stick it on a build agent or in SCC as part of a tools folder without including stuff that a build agent would never use.
Of course, this now has its own problems as v7 seems to use an activation model whereas with v6 you could just include the license file to your agents. (Not to mention the…
1 vote -
Provide dependency graph for refactoring planning
I would like to see another kind of dependency graph. It should be more like a map where dependencies flow from top to bottom or right to left. The difference is, that you can drill down from assemblies, to namespaces, to classes, to methods. All of this within one view.
For example: First I see a dependency graph containing all namespaces. When I click on namespace A, it shows me that this has dependencies to namespace B and C. Now I unwrap namespace B and see all classes and all dependencies from A to the classes, instead of the single…
4 votes -
Improve management of rules shared between projects
In addition to sharing custom rules between projects I want to be able to enable/disable rules among all my projects. I currently have 5 active ND projects, so if I want to turn off, for instance, "Nested types should not be visible" for all my projects, I have to go uncheck it in each project. Every time I tweak my rules, I have to go repeat these tweaks in all my ND projects.
Some sort of meta-project rules management would be an enormous effort saver.
In addition, once a set of "standard rules" are decided upon, it would be nice…1 vote -
Add support for dependency cycles detection for the code using dependency injection
Currently if code is made using dependency injection NDepend fails to detect cyclic dependencies. Sample code:
public interface Interface1 { void Foo(); }; public interface Interface2 { void Bar(); }; public class MyClass1 : Interface1 { private Interface2 _interface2; public MyClass1(Interface2 interface2) { _interface2 = interface2; _interface2.Bar(); } void Interface1.Foo() { } } public class MyClass2 : Interface2 { private Interface1 _interface1; public MyClass2(Interface1 interface1) { _interface1 = interface1; _interface1.Foo(); } public void Bar() { } }5 votes -
TFS 2015 Update 3 VSO Build Code Coverage Integration
Integrate NDepend into TFS 2015 Update 3 VSO Build technology, specifically with historical trending code coverage analysis in mind.
7 votes -
Allow to define colors on dependency graphs
Allow to choose a color for a code element on the dependency graph view and by default choose a color for the query targets and another one for the query results.
6 votes -
Advice on splitting applications
I have come across several examples in my development career where the code has become monolithic and shared amongst multiple applications. For example, a project that I worked on recently had two websites - one for internal admin and one for external and the code is not well-segmented into different assemblies.
It would be nice to be able to select two application projects and get an output for items used separately and shared. You can do this by querying but a simple method would be useful.
2 votes -
Highlight the IDE's currently selected method, class, and assembly in NDepend views
I'd love it if the Visual Studio add-in would highlight the location of the visual studio editor in the various NDepend views - particularly the code metrics tree map. I'd love to see where I am in code as I'm actively editing C# or VB .NET code.
3 votes -
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 -
Create profiles for different levels of experience
The UI can be overwhelming. I think it would be nice to have different profiles, e.g. for advanced and novice users.
The novice user should have a preset of settings which allow him only to see the basic features... just to create more overview.
Whereas the advanced user doesn't have to remove all the info messages/window.
6 votes -
Allow adding comments to disabled rules
It would be great if you can add a comment to a disabled rule. For some libraries we disable some of the rules and it would be great if we can put a remark why we disable a certain check. It would also be okay if we have to put it in the rule definition.
1 vote -
Enable search in Options
Just like in Visual Studio 2015, it would be nice to have a possibility to search in the options.
3 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 -
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
- Don't see your idea?