Relative paths in NSight Profiler

Hi,

I’m trying to set up some NSight Profiler .nvact files for the whole team to use, so that they can just launch a preconfigured profile instead of setting it all up themselves every time. However, I have run into a bit of a problem; all of the paths are fixed and fully resolved, and there does not seem to be any useful way to expand variables/macros.

So for example, my .nvact file has the path to the application stored as

D:\Project\bin\app.exe

But my teammate has his dev system set up differently, and his application is at

D:\Projects\Project\bin\app.exe

Obviously the profiler will not find the binary, and will be unable to launch.

I really want to be able to use the Visual Studio built in variables, so that I could have

$(SolutionDir)…\bin\app.exe

instead. This would be usable for all members of the team, regardless of where their code is checked out.

Is there some mechanism for expanding variables that I am missing? Or is this just not possible in the current version of NSight?

You might also want to post your question in the forum section dedicated to Nsight VSE:

https://devtalk.nvidia.com/default/board/84/nsight-visual-studio-edition/