-
Notifications
You must be signed in to change notification settings - Fork 17
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
v2.0: "undefined" is not valid json in #60
Comments
I had the same problem with VSCodium and dotnet 6.0 installed via the package manager on Debian. But it didn't recognize dotnet 6.0 and downloaded a portable version of 7.0 to use. |
A workaround for this seems to be adding |
A workaround from @yelvert didn't work for me unfortunately, at least not with the recent 2.7.25 and 2.0.436 versions. However I found a reason why it fails and a temporary solution until the proper fix is merged. Extension starts a debugger using the command defined here: So on Linux system it ends up with the command looking like: It looks like the installation path is taken from |
Thank you @mars-low. |
Added this workaround in v2.8.23. |
v2.8.23 on Win10 now looks like it does nothing. When I press F5, build process is started, and then nothing happens. It doesn't stop at breakpoints. And I don't see any error notification. |
VSCodium 1.82.1 with free-omnisharp 2.0.436. When I try to debug (F5) I get the following notification:
Debug is not started. With free-omnisharp 1.25.7 everything is OK.
P.S. Portable VSCodium, portable .NET SDK (7.0.400)
The text was updated successfully, but these errors were encountered: