Closed ankushdesai closed 5 years ago
Does it have something to do with the paths being hard-coded in the App.Config file?
I don't think this is a bug, but the intended current design. I believe this is related to the paths in the App.Config file, as you mentioned, and described here:
I think you need to override the environment variables as the above document mentions? @akashlal is that correct?
You can set a custom path by editing the file PSharpTester.exe.config
that sits alongside PSharpTester.exe
The documentation also says that these paths can be set on the environment as well.
overridden by environment variables with the same names as the app settings:
VSInstrToolPath
VSPerfCmdToolPath
This is useful in case you do not want to edit PSharpTester.exe.config
.
Thanks @akashlal and @pdeligia for the quick help. I will try this and re-open the issue if it doesnt work.
I am trying to run PSharpTester with the
/coverage:code
option and am getting the following error:Error: [PSharpTester] 'VSInstr' tool 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Team Tools\Performance Tools\x64\vsinstr.exe' not found.
I have the vsinstr installed in the following path:
D:\Microsoft Visual Studio\2017\Professional\Team Tools\Performance Tools\x64
I tried to run PSharpTester from the Developer Command Prompt and made sure that
vsinstr
in the path.