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)
![](https://secure.gravatar.com/avatar/14135fa38c0caab2ca05dec2332d433b?size=40&default=https%3A%2F%2Fassets.uvcdn.com%2Fpkg%2Fadmin%2Ficons%2Fuser_70-6bcf9e08938533adb9bac95c3e487cb2a6d4a32f890ca6fdc82e3072e0ea0368.png)
-
JamBo commented
Hi Patrick,
That would actually work great (for me at least). -
We can propose: the user copy manually the file VisualNDependOptions.xml in the NDepend project file (.ndproj) parent folder and it is then taken account, what do you think?
-
Ok we'll investigate
-
JamBo commented
Hi,
Indeed the the VisualNDependOptions.xml.
Exactly like that, much morw convenient when working on mulitple solutions, different locations/ organizations. -
Do you mean the VisualNDependOptions.xml file that is usually in C:\Users\$usr$\AppData\Roaming\NDepend ? You want its path to be specified in the .ndproj project file file and this way each project has its own options?