-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Installers respect DOTNET_SKIP_FIRST_TIME_EXPERIENCE=true, but should they? #8605
Comments
It's worse than that because calling
|
I would expect that would only happen if you had DOTNET_SKIP_FIRST_TIME_EXPERIENCE=true at installation, but not when running dotnet restore. Indeed option 2 suggests setting it to true. Can you confirm that this is what you see. |
That's correct -- assuming |
A "simple" hack to fix this in the installer could just be to have it always set |
I agree. The first run experience should always be executed for the native installers. cc @wli3 |
Also happening on a brand new system, first time install of latest SDK (2.1.400). Any dotnet command results in:
The sdk was installed from the MacOS package installer on a fresh system. |
I tried using a 'sudo dotnet' command but now I'm getting multiple exceptions:
|
Reported offline by @onovotny.
He had set the environment variable on his machine to workaround a bug in the first-time experience on an earlier build and then ended up without his fallback folder populated when he upgraded.
Is this by design or just fallout from a leaky implementation detail? I suspect the latter. It's debatable that we might want an option to avoid exploding all of the packages in to the fallback folder, but SKIP_FIRST_TIME_EXPERIENCE isn't an intuitive name for that when it actually impacts the step during installation.
At true RTM, the symptom of this would be that packages are pulled from nuget.org instead of the fallback folder, However, in interim builds, there can be packages in the fallback folder that are not on nuget.org and then the symptom is that restore will fail.
The text was updated successfully, but these errors were encountered: