-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
clarify how to get binaries if F5 results in error #8788
Conversation
The goal of this is to hopefully help contributors who might get stuck building the extension locally, like I did in #8745. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for helping improve the docs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, we should add a line about possibly needing to copy over the debugAdapters folder (i.e. cl.exe debugging wasn't working for me until after I did that). @WardenGnaw Any other debugger related steps should be documented?
There used to be a script that would automatically copy over the debugAdapters during However, to the move of .NET 5, it was unnecessary to copy specific binaries and now the guide in MIEngine suggests to use The whole point of this step was to delete the debugAdapters folder and replace it with ones you have locally built.
|
This commit addresses #8788 (comment).
This commit addresses #8788 (comment).
This commit addresses #8788 (comment).
This commit addresses #8788 (comment).
This commit addresses #8788 (comment).
This commit addresses #8788 (comment).
No description provided.