Improved Path Support: please implement an improvement to Path support such that I can use both relative path + path variables in the ndproj file.
This is important as I want to be able to:
add specific assemblies to the ndproj using a relative path. This means that when I branch, I don't need to update the default value to include the new branch name when using Visual NDepend
support two standard arguments used through our build process $(Configuration) and $(Platform)
Example of what I want to be able to do in he Path References screen (screenshots available on request):
Current Situation: Approach 1
Current Situation: Approach 2
Currently NDepend does not evaluate multiple path variables unless the whole path is prefixed with a path variable.
Your 'Path References' UI + implementation is very capable - great job. Please add this additional feature to really complete the feature!
this was done with v5.4 end of 2014, sorry for not closing this earlier
Marcus L commented
To be clear as to why Approach 2 doesn't work as well for us. Although a build script can always evaluate $(SourcePath), developers using Visual NDepend would have to update the default value for this field when we rebase source code. A screenshot illustrates my point better.
Support for $(Platform)\$(Configuration) at the end of a path is pretty standard need for us w/ the build process.