Skip to content
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

mono.exe not found in debug session #61

Open
KG2501 opened this issue Jan 23, 2020 · 0 comments
Open

mono.exe not found in debug session #61

KG2501 opened this issue Jan 23, 2020 · 0 comments

Comments

@KG2501
Copy link

KG2501 commented Jan 23, 2020

I have Visual Studio Code 1.41.1 installed with latest Mono-debug.
When I start debugging I get the following error:
mono --debug --debugger-agent=transport=dt_socket,server=y,address=127.0.0.1:50046 cscs.exe -d -inmem:0 -co:/debug:pdbonly -ac:2 c:\Users\Administrator\AppData\Roaming\Code\User\cs-script.user\new_script.cs
'"C:\Users\Administrator\AppData\Roaming\Code\User\cs-script.user\mono.exe"' is not recognized as an internal or external command,
operable program or batch file.

When I open a cmd.exe and enter just mono.exe I get the help for mono. So my path variable is correctly set to:
PATH=C:\Program Files\Mono\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files\Microsoft VS Code\bin;C:\Program Files\dotnet;C:\Users\Administrator\AppData\Local\Microsoft\WindowsApps
Why does visual studio code try to start mono.exe from the script directory? And why is there a double backslash before mono.exe?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant