-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Debugging Environment not set #2
Comments
Hello lisona. I've encountered the described problem myself, but haven't found any answer yet. This seems to be a limitation in Microsoft API. The code used so launch debugger is found at https://github.com/markusl/GoogleTestRunner/blob/master/GoogleTestRunner/GoogleTestExecutor.fs#L23 I don't know the internals of "LaunchProcessWithDebuggerAttached", but i suspect it should use the same debugger settings user has specified in the IDE. Regards, |
Hello Markus, I am a bit emberassed that I can't help any further, but I am neither a VS nor F# or .Net specialist. I don't even have VS2013, which is required to build the GoogleTestRunner. Kind regards, |
Just to say, I suffer the same problem here. The PATH is setup with paths to our dlls and thus need to be used in order to have the executable working... |
The settings from Properties-->Configuration Properties-->Debugging-->Environment are not used when running the tests (VS2012). In our project the environment contains additional path to load external libraries. GoogleTestRunner fails, when trying to detect the tests contained in the executable, because it cannot start the exe due to missing libraries. Unfortunately all possible error messages are swallowed too, which makes finding the cause considerably hard.
Is it possible, that the debugging environment is set during discovery of tests and possible error messages are displayed to the user?
The text was updated successfully, but these errors were encountered: