-
Notifications
You must be signed in to change notification settings - Fork 32
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
Start debugging in VSCode 1.56.0 #143
Comments
Thanks for reporting this issue to us! We will look into it. |
I also have same problem. |
@carlosmgilp @enevre @krebskyl
|
Objective Update the "debuggers->languages" part of package.json Abstractions During the discussion in microsoft/vscode#123881, @isidorn found that the "languages" in the "debuggers" part of package.json were over defined - we just need to list language id, instead of language object. With this change applied, the bug #143 is partially solved - now if there's a .lsp file opened, when pressing F5 to debug with VS Code 1.56.2, it doesn't require the existence of configuration file anymore. Tests performed Tested on VS Code 1.56.2 and 1.54.3; it's able attach to autocad on both of them (with a .lsp file opened).
Meanwhile, we are preparing for an official release to address this issue. |
I've gotten this to work by ensuring I have the process name filled out under "Workspace" as well as "User" under the extension settings. |
Solved, please:
|
Describe the bug
When trying to debug my code, it shows me a warning.
And I am clear that the extension is installed.
If I install an older version of VSCode, it works fine.
Desktop
The text was updated successfully, but these errors were encountered: