Restart needed after installing .NET Core Runtime and SDK?

user_3995644 0
Viewed 12122

We're about to deploy a netcore 2.0 application on production, but we need to install .NET Core Runtime and SDK first. Is a restart needed for the installation to take effect? Since it's production, we don't want that to happen.

asp.net-core-2.0 asp.net-core production-environment
4 Answers

We installed the following from here

  1. x64 Installer (SDK)
  2. x64 Installer (Runtime)
  3. Windows Server Hosting (Runtime)

There was no need to restart the machine and nothing blew up (:

user_39956440

If you are creating a Windows Service using the .NET Core SDK (Microsoft.Extensions.Hosting.WindowsServices) and deploying it in the target machine you need a restart (atleast a log off depending on the application you are running). Here is what happens.

  1. Install .NET Core Runtime
  2. Deploy a windows service.
  3. You will notice that the command line in the windows service will be "dotnet "
  4. Start the service. It will fail because it cannot find the tool "dotnet".
  5. This is because the service control manager (services.msc) is not aware of the dotnet command being added to the path. So you can either do a log off (or)restart to make sure things work.
user_8666700

You could just install Windows Server Hosting Bundle without SDK on your production machine (actually it should be).

But then you'll get 502.3 error, and you could add a element as follows into {YourProject}.csproj file, and then it'll work like a charm.

<PropertyGroup>
  <PublishWithAspNetCoreTargetManifest>false</PublishWithAspNetCoreTargetManifest>
</PropertyGroup>

Ref: https://github.com/dotnet/coreclr/issues/13542

user_36348670

With respect to either:

  • .NET 6.0 Desktop Runtime (v6.0.2) - Windows x64 Installer Link
  • .NET 6.0 Runtime (v6.0.2) - Windows x64 Installer Link

... a reboot is not required.

I didn't have time to test:

  • ASP.NET Core 6.0 Runtime (v6.0.2) - Windows Hosting Bundle Installer Link
  • ASP.NET Core 6.0 Runtime (v6.0.2) - Windows x64 Installer Link

... but agree with @MuqeetKhan that you should ideally have both a dev && testing lower environment before performing a production install. (Though, I also understand with smaller co's, that due to constraints & battles lost; this may not be possible.)

user_13275080
Related