Travis Schettler
My feedback
-
1 voteTravis Schettler
shared this idea
·
-
6 votes
An error occurred while saving the comment An error occurred while saving the comment Travis Schettler
commented
Thanks for the response Patrick. This seems like it should work, but it doesn't. The setting is added, but the existing user profile information is still present in the ndproj file. Attempts to remove it do not succeed, it just comes back again. Here's what I see in the ndproj file after setting the path with an environment variable:
<Dirs>
<Dir>C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.22</Dir>
<Dir>C:\Program Files\dotnet\sdk\NuGetFallbackFolder</Dir>
<Dir>C:\Users\tschettler\.nuget\packages</Dir>
<Dir>%userprofile%\.nuget\packages</Dir>
</Dirs>I prefer not to have any paths from the developer machine in the ndproj file since we plan to commit the file to source control, as per suggestion here: https://www.ndepend.com/docs/ndepend-storage-and-files#guidances-scm
Every other path referenced in the ndproj file can be modified to be developer-agnostic. The <Dirs/> element is driven mainly on the .NET Profile setting. I think the ideal solution would be to store these paths outside of the ndproj file and just store the .NET Profile setting in the ndproj file.
Travis Schettler
shared this idea
·
-
1 voteTravis Schettler
shared this idea
·
-
1 voteTravis Schettler
shared this idea
·
-
1 voteTravis Schettler
shared this idea
·
This actually exacerbates the issue, since this means the files will be continuously updated by different developers who use NDepend. Since we are managing these files in source control, this could result in a lot of unnecessary churn on these files.
Our goal is to start with a standard NDepend setup across all of our projects so they are all measured in the same way. This requires consistency in the project setup and we also want to require approval for changes to the ndproj file in order to ensure consistency. It is not ideal for the committed NDepend project file to change when NDepend loads the project, as this will almost always result in a change to the pre-configured NDepend project file.