Issue #66: Run dotnet restore before starting LS
#101
Merged
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
|
I'm wondering whether it wouldn't be better to wait for OmniSharp to include the LSP support out of the box rather than stacking workarounds for the deprecated nodejs wrapper. What do you think? |
Re-add previously removed workaround for OmniSharp/omnisharp-node-client#265 Signed-off-by: Lucas Bullen <[email protected]>
|
I think it is important to have this workaround in for now, until we have the support, as users are not aware of the required |
|
Ok, feel free to push to master then. |
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.
Re-add previously removed workaround for
OmniSharp/omnisharp-node-client#265
Signed-off-by: Lucas Bullen [email protected]