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
-
VSTS Plugin Dashboard should allow full screen view
The VSTS/DevOps plugin dashboard view on my laptop is really small with large lists.
It would really help if you provided a full-screen mode for portions of the reports like VSTS/DevOps does on other parts of the system.
For example, if I look at the Issues/Debt screen, and select "Critical Issues" on the left for example, the list can be quite long, but I can only see 10 items at a time with my laptop.
Not to mention that above that content there are two big divs that are probably wasting space.
One that says "Double click an issue to…
3 votes -
Add integration and documentation for AWS CodeBuild
AWS CodeBuild is our go-to solution for building and testing DotNet Core solutions. This would be similar to Appveyor, but benefit from inheriting the IAM security model and S3 storage of artifacts. CodeBuild also recently added Reports which provide a way to track test metrics over time. Seems like a perfect fit.
3 votes -
Make it easier to update the software
Why should we have to download anything to update the software? Provide us a button to click to perform an Update.
3 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 -
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 -
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 -
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 -
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 -
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 -
Define the first Analysis Result of a Project as a baseline for further Analysis Results
Define the first Analysis Result of a Project as a baseline for further Analysis Results (not applicable to Temporary projects)
2 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 -
Reuse NDepend's Technical Debt and Quality Gate functionality with other rule sources
The introduction of technical debt assessment and quality gates in NDepend 2017 is a very welcome addition. However, the scope of these features (and others like TFS integration and baselines) is restricted to NDepend. This scope is too narrow for those of us that make use of other rule sources such as FxCop, StyleCop, Code Cracker, Refactoring Essentials, OWASP Dependencies, SonarQube, custom written Roslyn rules et al. We would like to use NDepend's features but the scope means that it is only telling part of the story and unfortunately this isn't enough for it to be usable.
We would like…
2 votes -
Integrate deeper with Code Edition panel in VS
Actually the code element right clicked is inferred from the method body, type body, namespace body where the right-click occur. Provide a finer inference of the code element right clicked based on symbol names right-clicked (like if a type name in a method signature is right clicked, infer the type instead of the method).
2 votes -
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 -
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 -
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 -
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 -
1 vote
-
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
- Don't see your idea?