Runtime: Uninstalling 1.1.0-preview1 runtime breaks 1.0.1 runtime - Fix in 2.0.x

Created on 3 Nov 2016  路  14Comments  路  Source: dotnet/runtime

Steps to reproduce

  1. Install 1.0.1 runtime
    (I see that the C:\Program Files\dotnet\host\fxr\1.0.1 directory gets created)
  2. Install 1.1.0-preview1 runtime
  3. Uninstall 1.1.0-preview1 runtime
    (There is no longer a C:\Program Files\dotnet\host directory)

    Expected behavior

$ dotnet

Microsoft .NET Core Shared Framework Host

  Version  : 1.0.1
  Build    : cee57bf6c981237d80aa1631cfe83cb9ba329f12

Usage: dotnet [common-options] [[options] path-to-application]

Common Options:
  --help                           Display .NET Core Shared Framework Host help.
  --version                        Display .NET Core Shared Framework Host version.

Options:
  --fx-version <version>           Version of the installed Shared Framework to use to run the application.
  --additionalprobingpath <path>   Path containing probing policy and assemblies to probe for.

Path to Application:
  The path to a .NET Core managed application, dll or exe file to execute.

If you are debugging the Shared Framework Host, set 'COREHOST_TRACE' to '1' in your environment.

To get started on developing applications for .NET Core, install .NET SDK from:
  http://go.microsoft.com/fwlink/?LinkID=798306&clcid=0x409

Actual behavior

$ dotnet
A fatal error occured, the required library hostfxr.dll could not be found at C:\Program Files\dotnet

Environment data

dotnet --info output:

A fatal error occured, the required library hostfxr.dll could not be found at C:\Program Files\dotnet

cc @joeloff @jhkimnew

area-Infrastructure-installer area-Setup blocking-release

Most helpful comment

@shirhatti Workaround in windows: if you repair the previous 1.0.1 install, you get your expected behavior.

All 14 comments

I believe @schellap has this fixed in 1.1.0 final builds. @schellap can you confirm and if so, close this issue.

is there any workaround or fix for this issue

my system is hosed currently with the same problem

Have you tried to reinstall the 1.0.1 SharedFW again?

@gkhanna79, this issue has different repro steps. Will take a look.

@schellap Yes i have done that as well - but it doesnt work... the only way it to roll forward it seems

@shirhatti Workaround in windows: if you repair the previous 1.0.1 install, you get your expected behavior.

I just ran into this issue after I installed and uninstalled the .NET Core SDK 2.0. Is there a workaround?

@Ponant If the 1.x runtime is installed you can try repairing that.

@joeloff , I am repairing VS 2017 RC4 at the moment, I expect it to work.
EDIT, it does.

Assigning this to you @rakeshsinghranchi and @vivmishra

@rakeshsinghranchi Do you have the 1.1.x and 1.0.x version of the issue filed? If so, please close this.

Thanks It's working now.

Was this page helpful?
0 / 5 - 0 ratings