You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
pc B installed dotnet core 2.0 runtime win64, os is windows server 2008 r2 x64 with SP1
pc A use VS2017 write a asp.net core 2.0 project, and published to a dir, with <PublishWithAspNetCoreTargetManifest>true</PublishWithAspNetCoreTargetManifest>
on A use dotnet dir\x.dll no error
copy dir to B, on B dotnet dir\x.dll get above error
if turn <PublishWithAspNetCoreTargetManifest>false</PublishWithAspNetCoreTargetManifest>, it's worked, but I don't want this
The text was updated successfully, but these errors were encountered:
In addition to the .NET Core Runtime, you will need to install the ASP.NET Core Runtime Store on the target machine (in this case pc B). The Runtime Store is automatically installed via the Windows Server Hosting installer (see https://www.microsoft.com/net/download/core#/runtime for the most up to date download link). The reason this works on the developer machine (in this case pc A) is because the Runtime Store is installed via the .NET Core SDK.
Like John indicated, you built your application using the asp.net store, which is on by default, so in order to run it, wherever you deploy it, you need the asp.net runtime store installed as well. Alternatively, you can turn off using the store when building your app by setting <PublishWithAspNetCoreTargetManifest>false<PublishWithAspNetCoreTargetManifest>. Note that if you set this, you will have to re-publish your app.
Environment and Description
<PublishWithAspNetCoreTargetManifest>true</PublishWithAspNetCoreTargetManifest>
<PublishWithAspNetCoreTargetManifest>false</PublishWithAspNetCoreTargetManifest>
, it's worked, but I don't want thisThe text was updated successfully, but these errors were encountered: