We would like to be able to use Visual Studio variables like $(ProjectDir) in the NTVS properties dialog. That would really speed up our workflows and help prevent collisions between developers.
NTVS stores these settings in an NJSPROJ file. We have this file in source control and it is shared by our whole team. We struggle with this because all of the paths in properties have to be absolute to work. Each developer has to tweak 'node.exe path', 'working directory' and 'environment variables' to point to paths on their individual system every time the file is changed. Then they have to be very careful in checking in any changes to that file.
We solved similar problems in C++ VCXPROJ files by using paths that are relative to VS variables, like $(ProjectDir). But, unfortunately, NTVS doesn't accept those variables. Nor does it allow for relative paths.
Could the NTVS settings dialog be beefed up to allow VS variables?
NTVS stores these settings in an NJSPROJ file. We have this file in source control and it is shared by our whole team. We struggle with this because all of the paths in properties have to be absolute to work. Each developer has to tweak 'node.exe path', 'working directory' and 'environment variables' to point to paths on their individual system every time the file is changed. Then they have to be very careful in checking in any changes to that file.
We solved similar problems in C++ VCXPROJ files by using paths that are relative to VS variables, like $(ProjectDir). But, unfortunately, NTVS doesn't accept those variables. Nor does it allow for relative paths.
Could the NTVS settings dialog be beefed up to allow VS variables?