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
6 results found
-
Make the settings file location customizable
When the location is customizable we can easier move the settings fiile between machines (par example as part of a solution)
1 vote -
Allow external settings file for trend metrics
Allow TrendMetrics section to pull chart configuration from an external settings file. This would allow customizations to the charts to be shared across all projects. It would also result in fewer changes when managing ndproj files using source control, since updates to these settings would not result in changes to the ndproj file.
3 votes -
Add support for .NET Core packaged application analysis
When .NET Core assemblies and applications are built and packaged using dotnet CLI (e.g., "dotnet pack") the build output isn't a folder full of assemblies the way it was in classic .NET - it's a NuGet .nupkg file with the assembly (or full application) inside.
In the case of applications, this includes not only the entry point (e.g., "MyApplication.exe") but also any dependent assemblies required to make the app run. That even means all of the base framework assemblies ("System.Collections.dlll") - there is no reference to any installed .NET Framework. The dotnet CLI and runtime take care of that and…
13 votes -
Ability to analyze NuGet packages
There are currently project types for analyzing a project/solution and for analyzing a folder full of assemblies.
Much of my work lately has been in creating smaller, standalone "framework" sorts of packages on an internal NuGet feed that different applications can consume. There isn't "a master project" that has all of these packages working together; instead it's different combinations of the packages.
I'd like to be able to analyze all of these packages in a single report without having to either manually download them all or create a "fake" project just for the sake of referencing them.
One way to…
39 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 -
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
- Don't see your idea?