Skip to content
This repository was archived by the owner on Jan 12, 2024. It is now read-only.

Conversation

@vxfield
Copy link
Member

@vxfield vxfield commented Nov 25, 2020

This PR mitigates issue #737 by:

  1. Adding a global.json in the LanguageServer folder
  2. Forcing the Working Directory of the LanguageServer to be the same as the. LanguageServer is (and. therefore using the global.json from step above)
  3. Not quitting the LanguageServer if there was an issue with the MSBuildLocator when .NET Core SDK 3.1 is not found
  4. Check if .NET Core SDK 3.1 is not installed and display a message to the user with an option to download it (opens the download page) and asking the user to restart VS/Code.

vxfield and others added 11 commits November 25, 2020 01:35
(cherry picked from commit 28e79dd)
Co-authored-by: Sarah Marshall <33814365+samarsha@users.noreply.github.com>
(cherry picked from commit f2cd93b)
Co-authored-by: Sarah Marshall <33814365+samarsha@users.noreply.github.com>
(cherry picked from commit de463e0)
Co-authored-by: Sarah Marshall <33814365+samarsha@users.noreply.github.com>
(cherry picked from commit 7911bd5)
Co-authored-by: Sarah Marshall <33814365+samarsha@users.noreply.github.com>
(cherry picked from commit c19177d)
(cherry picked from commit 283cecd)
@vxfield
Copy link
Member Author

vxfield commented Nov 25, 2020

@SamarSha, @bettinaheim: this is exactly the same approved PR #753 but now targeting the main branch.

"version": "3.1.100",
"rollForward": "latestFeature"
}
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should have only one global.json that applies to the compiler repository. Currently, the global.json at the root of the repository also sets the SDK version to 3.1, but it may be updated to support 5 soon. In that case, running dotnet from the LanguageServer folder will require 3.1, but may use 5 when run from any other folder.

Since this global.json is intended to only be used by the language server after it's built and running, is it possible for it to have a different name in the source folder that dotnet won't recognize, but have it be renamed to global.json in the output directory?

@vxfield vxfield closed this Jan 14, 2021
@vxfield vxfield deleted the xfield/dotnet-sdk-version branch January 14, 2021 22:14
@bamarsha bamarsha restored the xfield/dotnet-sdk-version branch January 19, 2021 21:28
@bamarsha bamarsha deleted the xfield/dotnet-sdk-version branch January 19, 2021 21:32
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