You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Installs the .NET SDK specified in the global.json file at the root of this repository,
6
-
along with supporting .NET Core runtimes used for testing.
5
+
Installs the .NET SDK specified in the global.json file at the root of this repository,
6
+
along with supporting .NET Core runtimes used for testing.
7
7
.DESCRIPTION
8
-
This MAY not require elevation, as the SDK and runtimes are installed locally to this repo location,
9
-
unless `-InstallLocality machine` is specified.
8
+
This MAY not require elevation, as the SDK and runtimes are installed locally to this repo location,
9
+
unless `-InstallLocality machine` is specified.
10
10
.PARAMETERInstallLocality
11
-
A value indicating whether dependencies should be installed locally to the repo or at a per-user location.
12
-
Per-user allows sharing the installed dependencies across repositories and allows use of a shared expanded package cache.
13
-
Visual Studio will only notice and use these SDKs/runtimes if VS is launched from the environment that runs this script.
14
-
Per-repo allows for high isolation, allowing for a more precise recreation of the environment within an Azure Pipelines build.
15
-
When using 'repo', environment variables are set to cause the locally installed dotnet SDK to be used.
16
-
Per-repo can lead to file locking issues when dotnet.exe is left running as a build server and can be mitigated by running `dotnet build-server shutdown`.
17
-
Per-machine requires elevation and will download and install all SDKs and runtimes to machine-wide locations so all applications can find it.
11
+
A value indicating whether dependencies should be installed locally to the repo or at a per-user location.
12
+
Per-user allows sharing the installed dependencies across repositories and allows use of a shared expanded package cache.
13
+
Visual Studio will only notice and use these SDKs/runtimes if VS is launched from the environment that runs this script.
14
+
Per-repo allows for high isolation, allowing for a more precise recreation of the environment within an Azure Pipelines build.
15
+
When using 'repo', environment variables are set to cause the locally installed dotnet SDK to be used.
16
+
Per-repo can lead to file locking issues when dotnet.exe is left running as a build server and can be mitigated by running `dotnet build-server shutdown`.
17
+
Per-machine requires elevation and will download and install all SDKs and runtimes to machine-wide locations so all applications can find it.
if ($anythingInstalled-and ($InstallLocality-ne'machine') -and!$env:TF_BUILD-and!$env:GITHUB_ACTIONS) {
231
+
Write-Warning".NET Core runtimes or SDKs were installed to a non-machine location. Perform your builds or open Visual Studio from this same environment in order for tools to discover the location of these dependencies."
0 commit comments