blocks|key|2477547|text|我们从这里安装了以下代码|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2477548|x64安装程序(SDK)|ordered-list-item|2477549|x64安装程序(运行时)|2477550|Windows宿主(运行时)|2477551|没有必要重新启动这台机器，也没有什么爆炸。|2477552|entityMap|0|LINK|mutability|MUTABLE|url|https://www.microsoft.com/net/download/windows^0|3|2|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|F|7|Y|8|@]|9|@]|C|$]]|$1|G|3|H|5|F|7|Z|8|@]|9|@]|C|$]]|$1|I|3|J|5|F|7|10|8|@]|9|@]|C|$]]|$1|K|3|L|5|6|7|11|8|@]|9|@]|C|$]]|$1|M|3|-4|5|6|7|12|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]]]

We installed the following from <a href="https://www.microsoft.com/net/download/windows" rel="noreferrer">here</a>

<ol>
<li>x64 Installer (SDK)</li>
<li>x64 Installer (Runtime)</li>
<li>Windows Server Hosting (Runtime)</li>
</ol>

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

blocks|key|426765|text|如果要使用Windows+(Microsoft.Extensions.Hosting.WindowsServices)创建Windows并将其部署到目标计算机中，则需要重新启动(至少根据正在运行的应用程序进行注销)。下面是发生的事情。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|426766|安装.NET核心运行时|ordered-list-item|426767|部署一个windows服务。|426768|您将注意到windows服务中的命令行将是"dotnet“。|426769|开始服务。它将失败，因为它找不到工具"dotnet“。|426770|这是因为服务控制管理器(services.msc)不知道dotnet命令正在添加到路径中。因此，您可以执行注销(或)重新启动，以确保一切正常。|426771|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|Q|8|@]|9|@]|A|$]]|$1|G|3|H|5|D|7|R|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|S|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|T|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|N|$]]

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.

<ol>
<li>Install .NET Core Runtime</li>
<li>Deploy a windows service. </li>
<li>You will notice that the command line in the windows service will be "dotnet "</li>
<li>Start the service. It will fail because it cannot find the tool "dotnet".</li>
<li>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.</li>
</ol>

blocks|key|2477568|text|您可以在生产机器上安装Windows托管捆绑(实际上应该是这样)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2477569|但是，您将得到502.3错误，您可以将如下所示的元素添加到{YourProject}.csproj文件中，然后它将像一个符咒一样工作。|2477570|<PropertyGroup>
++<PublishWithAspNetCoreTargetManifest>false</PublishWithAspNetCoreTargetManifest>
</PropertyGroup>|code-block|syntax|javascript|2477571|参考文献：https://github.com/dotnet/coreclr/issues/13542|2477572|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/dotnet/coreclr/issues/13542^0|B|B|0|0|0|5|1A|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Z|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|10|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|11|8|@]|D|@$9|12|A|13|1|14]]|E|$]]|$1|O|3|-4|5|6|7|15|8|@]|D|@]|E|$]]]|P|$Q|$5|R|S|T|E|$U|V]]]]

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.

<pre><code>&lt;PropertyGroup&gt;
 &lt;PublishWithAspNetCoreTargetManifest&gt;false&lt;/PublishWithAspNetCoreTargetManifest&gt;
&lt;/PropertyGroup&gt;
</code></pre>

Ref: <a href="https://github.com/dotnet/coreclr/issues/13542" rel="nofollow noreferrer">https://github.com/dotnet/coreclr/issues/13542</a>

blocks|key|842476|text|在以下两方面：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|842477|.NET+6.0桌面运行时(v6.0.2)+-+Windows+x64安装程序链接|unordered-list-item|offset|length|842478|.NET+6.0运行时(v6.0.2)+-+Windows+x64安装程序链接|842479|..。不需要重新启动。|842480|我没有时间去测试：|842481|ASP.NET+Core6.0运行时(v6.0.2)+-+Windows安装程序链接|842482|ASP.NET+Core6.0运行时(v6.0.2)+-+Windows+x64安装程序链接|842483|..。但是，您同意@MuqeetKhan的观点，即在执行生产安装之前，您应该同时拥有一个开发&测试更低的环境。(不过，我也从小公司了解到，由于限制和战败，这可能是不可能的。)|842484|entityMap|0|LINK|mutability|MUTABLE|url|https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/runtime-desktop-6.0.2-windows-x64-installer|1|https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/runtime-6.0.2-windows-x64-installer|2|https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/runtime-aspnetcore-6.0.2-windows-hosting-bundle-installer|3|https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/runtime-aspnetcore-6.0.2-windows-x64-installer^0|0|13|2|0|0|11|2|1|0|0|0|14|2|2|0|18|2|3|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|17|8|@]|9|@$E|18|F|19|1|1A]]|A|$]]|$1|G|3|H|5|D|7|1B|8|@]|9|@$E|1C|F|1D|1|1E]]|A|$]]|$1|I|3|J|5|6|7|1F|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|1G|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|1H|8|@]|9|@$E|1I|F|1J|1|1K]]|A|$]]|$1|O|3|P|5|D|7|1L|8|@]|9|@$E|1M|F|1N|1|1O]]|A|$]]|$1|Q|3|R|5|6|7|1P|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z]]|10|$5|V|W|X|A|$Y|11]]|12|$5|V|W|X|A|$Y|13]]|14|$5|V|W|X|A|$Y|15]]]]

With respect to either:
<ul>
<li>.NET 6.0 Desktop Runtime (v6.0.2) - Windows x64 Installer <a href="https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/runtime-desktop-6.0.2-windows-x64-installer" rel="nofollow noreferrer">Link</a></li>
<li>.NET 6.0 Runtime (v6.0.2) - Windows x64 Installer <a href="https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/runtime-6.0.2-windows-x64-installer" rel="nofollow noreferrer">Link</a></li>
</ul>
... a reboot is not required.
I didn't have time to test:
<ul>
<li>ASP.NET Core 6.0 Runtime (v6.0.2) - Windows Hosting Bundle Installer <a href="https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/runtime-aspnetcore-6.0.2-windows-hosting-bundle-installer" rel="nofollow noreferrer">Link</a></li>
<li>ASP.NET Core 6.0 Runtime (v6.0.2) - Windows x64 Installer <a href="https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/runtime-aspnetcore-6.0.2-windows-x64-installer" rel="nofollow noreferrer">Link</a></li>
</ul>
... but agree with @MuqeetKhan that you should ideally have both a dev &amp;&amp; testing lower environment before performing a production install. (Though, I also understand with smaller co's, that due to constraints &amp; battles lost; this may not be possible.)

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.

Restart needed after installing .NET Core Runtime and SDK?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

我们即将在生产上部署一个NetCore2.0应用程序，但是我们需要首先安装.NET核心运行时和SDK。是否需要重新启动安装才能生效？既然是生产，我们就不想发生这种事。

问安装.NET核心运行时和SDK后需要重新启动吗？
EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问安装.NET核心运行时和SDK后需要重新启动吗？EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问安装.NET核心运行时和SDK后需要重新启动吗？
EN