This repository was archived by the owner on Jan 12, 2024. It is now read-only.
Using NuGet.ProjectModel from the install path to avoid version conflicts #566
Conversation
This file contains hidden or 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
anpaz
approved these changes
Aug 12, 2020
anpaz
approved these changes
Aug 12, 2020
ricardo-espinoza
changed the title
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This change removes the dependency on NuGet.ProjectModel from the LanguageServer project and instead relies on the installed version of the binary. This change intends to avoid the dependency between the .Net Core SDK version and NuGet in MSBuildLocator. See issue #86 for additional reference.