Update CONTRIBUTING.md - using VSCode Extension with WSL2 #972
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
@@ Coverage Diff @@
## main #972 +/- ##
=======================================
Coverage 94.33% 94.33%
=======================================
Files 316 316
Lines 14771 14771
Branches 12 12
=======================================
Hits 13934 13934
Misses 837 837
Flags with carried forward coverage won't be shown. Click here to find out more.
|
miqm
force-pushed
the
contributing-with-wsl2
branch
from
9806502 to
c8115a5
Compare
anthony-c-martin
approved these changes
Nov 25, 2020
|
Thanks for updating this! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Current instruction, how to contribute using WSL was not good. It was causing issues with "stock" Bicep extension installed.
When we set the env variable in the .vscode-server/server-env-setup - it was also used by the "stock" extension. Now, when the current development version uses .NET5 and the stock still uses dotnet core 3.1, bicep language server couldn't load.
Removing the environment variable and symbolic linking Lang server build output resolves this issue.
However, I'm not entirely sure if and how it will affect setting up breakpoints.