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

clarify how to get binaries if F5 results in error #8788

Merged
merged 10 commits into from
Feb 18, 2022
Merged

clarify how to get binaries if F5 results in error #8788

merged 10 commits into from
Feb 18, 2022

Conversation

hamirmahal
Copy link
Contributor

No description provided.

@hamirmahal
Copy link
Contributor Author

The goal of this is to hopefully help contributors who might get stuck building the extension locally, like I did in #8745.

Copy link
Collaborator

@sean-mcmanus sean-mcmanus left a 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.

Copy link
Collaborator

@sean-mcmanus sean-mcmanus left a 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?

@WardenGnaw
Copy link
Member

There used to be a script that would automatically copy over the debugAdapters during prepublish.

However, to the move of .NET 5, it was unnecessary to copy specific binaries and now the guide in MIEngine suggests to use debugServer instead of copying over specific binaries.

The whole point of this step was to delete the debugAdapters folder and replace it with ones you have locally built.

  • (optional) Set an environment variable CPPTOOLS_DEV=1.
    * This enables the local developer workflow when testing the debugger, copying dependencies from the node_modules folder. Testing the language server does not require this step.

@sean-mcmanus sean-mcmanus merged commit fcd74cb into microsoft:main Feb 18, 2022
@hamirmahal hamirmahal deleted the patch-1 branch February 20, 2022 23:02
@github-actions github-actions bot locked and limited conversation to collaborators Apr 5, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants