When the location is customizable we can easier move the settings fiile between machines (par example as part of a solution)

We presently are using the Team City plugin and would like to keep quality gates enabled, but not prevent them from failing builds. We have the "one of build steps exited with an error" failure condition enabled and are constrained by other build steps to leave this enabled.

There is a /ForceReturnZeroExitCode command line option, but the same setting does not appear to exist for the TeamCity plugin. Please advise on whether this can be added to the plugin.

Thanks!

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.

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.

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.

Would be perfect if we could have metrics regarding duplicated code.

We could use it to then create rules and issues regarding the increase of duplicated code and also count it as technical debt.

It would be great to have a plugin for that.
Rider is fastest IDE and can work with much bigger solutions than VS can do. Most of our projects can't be even opened in the VS.

NDepend is a great tool for our .NET Core C# Back-End code analysis. It would be very nice if the new version would support the Front-End framework such as Angular (TypeScript) as well.

It should be possible to change the behavior of the mouse wheel for the Dependency Matrix.

Most of the time I want to scroll with the mouse wheel. For zooming could a Key+Mouse wheel used (e.g. Control+Mouse wheel).

Maybe I did not found it in the settings but, if not available, an option to approve or disable error reports send from NDepend to http://www.ndepend.com/ErrorLog.aspx as it includes a lot of data would be helpfull

We've moved from portable to embedded PDBs for our .NET projects - this means there is no longer a separate PDB file and the PDB information is embedded in the assembly. Please can NDepend support this so that queries using .PDBFound and NbLinesOfCode etc. continue to work?

Please support NDepend for builds which are running inside (linux) dockerfiles.

Hi Patrick,
the Font of the text in the Dependency Graph are extremely different in size.

The bigger are huge and the other so tiny to be unreadable.

This makes the graph much less usable
https://i.imgur.com/d5GUtby.png

My suggestion, use the font maximum size to 16px and minimum size to 7 px and use all the available space.

Please make the setup a bit easier to understand. I am a new user for Ndepend and i spent 30 mins trying to create a dependency graph of a existing project and in the end just gave up!

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.

We've a strict rule that every public member must be documented via xml comments, we need a way to find pieces of code that violate this rule.

NDepend is great but it definitely won't be able to cover all requirements for all customers, so, it'll be much better if we can extend NDepend !
In my organization, we've a lot of rules that share some logic so I need to encapsulate this logic in a single extension method either in a C# dll or a CQLinq query and reuse it anywhere.

Any plans in the works to create rules that enforce IDesign practices & principles (http://www.idesign.net/)?

I'd like to query for instances of the Select N+1 problem. Where database code is happening within a loop resulting in 'N' database queries for each iteration of the loop where one or two well-designed queries would do.

This could be implemented by searching for any method calls to a sub-typer of IRepository<T> or Repository<T> that occurs within a for, foreach or Enumerable loop.