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
9 results found
-
Update .NET Profile Directory Resolution
When using a .NET Profile, the NuGet packages directory stored in the <Dirs> element of the project is fully resolved to include the username. This poses a problem when committing the ndproj file to source control since the project settings are specific to a developer machine. It would be better to use %userprofile% instead:
%userprofile%\.nuget\packagesEven further, would it be best to just store the .NET Profile configuration itself in the ndproj project file instead of the corresponding paths? The resolved paths could possibly be saved in the suo file instead. This would also help resolve issues when there are…
6 votesCompleted with NDepend version 2022.2.0
-
DebtSettings handling when SettingsFilePath is set
When storing debt settings in an external .ndsettings file, the settings are still pulled in to the ndproj file when the first scan is run. There should be an option to prevent these settings from being copied into the ndproj file. When managing ndproj files using source control, this would lead to fewer changes since the when the external ndsettings file is changed, it would not impact the ndproj files referencing it.
1 voteComplete with version 2022.2.1
-
Remove storage of assembly names from NDepend project file
When NDepend analysis is run for the first time, it adds a list of framework assemblies to the ndproj file, in the <FrameworkAssemblies> section. There doesn't appear to be a way to prevent this from happening. When managing ndproj files in source control, this could lead to additional updates to the ndproj file whenever references within the projects are added or removed. It would be ideal to have an option to prevent this from happening, with these assemblies always being assessed against the build.
1 voteCompleted with NDepend version 2022.2.0
-
Support for Web Sites (WebForms/MVC)
At this moment it is not intuitive and very hard to analyze Web sites with ndepend will be very nice if I could get site analyzed in few button clicks
62 votesActually first-class support for ASP.NET MVC (Core or Fx) occured in v2017.3 and we just noticed that this point was still open in May 2020.
-
Reference VS solutions from the NDepend Project > Code to Analyze
In addition to references assemblies to analyze from NDepend project, make possible to reference also one or several VS solutions. Assemblies could then be resolved from a defined VS solutions configuration. Also a filter by name system would be handy to filter for example tests assemblies from the VS solutions.
24 votesIt is possible to reference VS soltuion and project from NDepend Project Properties > Code to Analyze panel https://www.ndepend.com/docs/ndepend-assemblies-resolving#resolving-assemblies-from-visual-studio-solutions
-
Provide sample project which reflects NDepend abilities for newbies
Provide sample project which reflects NDepend abilities for newbies
0 votes -
Make possible to have files of Code Rules shared amongst NDepend Projects
Make possible to have files of Code Rules shared amongst NDepend Projects
66 votesWe just released NDepend v6 that now make possible to have files of Code Rules shared among NDepend Projects.
http://www.ndepend.com/ndepend-v6You can now create your quality profiles in rule files and shared them among all your enterprise projects.
You can download v6 Release Candidate 1 to try it.
Your feedback at support@ndepend.com will be more than welcome.
You can also re-use your NDepend UserVoice votes for further feature request! -
7 votes
Done in the new version v5.2. We also added support for UNC netwrok path and marco/variable facilities like in $(SolutionDir)
-
Support UNC Paths and Shared Drives paths
Support UNC Paths and Shared Drives paths for files and dirs paths referenced by NDepend Projects
4 votesDone in the new version v5.2. We also added support for path prefixed with environment variable and macro/variable facilities like in $(SolutionDir)
- Don't see your idea?