dotnet-install.ps1 installs locally even when same version is already installed globally

[flcdrg]

Steps to reproduce

1. On a machine that already has 2.2.101 SDK installed
2. .\dotnet-install.ps1 -Version 2.2.101

Expected behavior

Do nothing.

Maybe provide a -Force parameter so that only when that is given, do you still install the version

Actual behavior

Version is installed into c:\users\USERNAME\AppData\Local\Microsoft\dotnet, even if it was already installed in C:\Program Files\dotnet\sdk

Environment data

dotnet --info output:

.NET Core SDK (reflecting any global.json):
 Version:   2.2.101
 Commit:    236713b0b7

Runtime Environment:
 OS Name:     Windows
 OS Version:  6.3.9600
 OS Platform: Windows
 RID:         win81-x64
 Base Path:   C:\Program Files\dotnet\sdk\2.2.101\

Host (useful for support):
  Version: 2.2.0
  Commit:  1249f08fed

.NET Core SDKs installed:
  1.0.0-preview2-003156 [C:\Program Files\dotnet\sdk]
  2.1.200 [C:\Program Files\dotnet\sdk]
  2.1.201 [C:\Program Files\dotnet\sdk]
  2.1.202 [C:\Program Files\dotnet\sdk]
  2.1.302 [C:\Program Files\dotnet\sdk]
  2.1.401 [C:\Program Files\dotnet\sdk]
  2.1.403 [C:\Program Files\dotnet\sdk]
  2.2.100 [C:\Program Files\dotnet\sdk]
  2.2.101 [C:\Program Files\dotnet\sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.3 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.2.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.3 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.2.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 1.0.3 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.0.7 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.0.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.3 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.2.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]

To install additional .NET Core runtimes or SDKs:
  https://aka.ms/dotnet-download

[peterhuene]

@johnbeisner is this something the install script should implement?

[johnbeisner]

Initial thoughts:
The two installation points, global and local, aren't completely interchangeable. Although we can essentially merge the two by enabling multi-level lookup, a common scenario is to isolate the local SDKs from the global SDKs by disabling multi-level lookup. In this way, machine state variants can be eliminated from build and/or test functions. Since many organizations depend on the current behavior for their build/test, asking them to change the call to dotnet-install.ps1 seems intractable. The way to implement would be an 'opt-in' flag.

[flcdrg]

An opt-in flag sounds reasonable. Something like -SkipIfInGlobal ?

[donJoseLuis]

The need tracked in this issue should be a requirement in the re-engineering effort. Moving to the re-engineering project.

[bekir-ozturk]

Hi,

The scripts are being put into "maintenance mode". This means that the scripts and their ecosystem (i.e. website and feeds) will continue to be monitored, but no new features will be delivered. We are still committed to maintaining the scripts’ high availability and we will quickly respond to any incidents.

As part of this effort, we are closing the issues that aren't planned to be delivered. Unfortunately, this issue is one of those that didn't make the cut, and therefore will be closed.
If you think this is a must-fix issue before maintenance mode begins, please feel free to comment.

Thanks

[bb010g]

@bekir-ozturk Is there a successor to these install scripts that is or will be delivering new features?

[bekir-ozturk]

Hi @bb010g,
I'm no longer with the project. Hopefully, @MichalPavlik and @donJoseLuis can shed some light on the matter 🙂

[YuliiaKovalova]

HI @bb010g ,

We are still in maintenance mode and do not plan to implement any new features.

[MV10]

Seems to me the repo README should note that they're in maintenance mode. People are still requesting new features (and a build script written by someone else just nuked my Program Files SDK installation by running this thing without warning, so that's half my day wasted on cleanup).