ASPNETCoreModule not installed with .NET Core SDK

问题:

I installed VS 2017 along with .NET Core SDK on Windows 10. But it did not install ASPNETCoreModule as shown in figure 2 below. I thought .NET Core SDK should have installed it implicitly - and one does not have to install it separately. NOTE: I'm trying to publish my asp.net core app to IIS and the publish process requires ASPNETCoreModule as explained in the above link and also in this official MSDN article.

ASPNETCoreModule is missing:

回答1:

ASP.NET Core Module is installed separately from the SDK. You can download the current version 2.0.0 here. https://github.com/dotnet/core/blob/master/release-notes/download-archives/2.0.0-download.md#windows-server-hosting

See https://github.com/dotnet/core/blob/master/release-notes/download-archive.md for a list of other releases.

回答2:

ASP.NET Core Module is installed separately from the SDK

It's not true since release of 2.1 . I'm experiencing the same issue on Windows Server 2016. Module was installed on developer PC after uninstalling old versions / installing 2.1 few time, but still struggling with the same issue on 2016. %SystemRoot%\system32\inetsrv\aspnetcore.dll is still missing.

回答3:

In order to run .net core apps on IIS you need to have installed the ASP.NET Core Module ( the way it works is explained here ) that comes:
1 - with the SDK 2.1,
2 - With the Hosting Bundle Installer that bundles the .Net Core and the ASP.NET Core Runtime into a single bundler.

you can have both from the download page

If you are a developer computer you already have the Module with the SDK, I think is better to have on Sever computer only the hosting bundle

回答4:

First, you need to check your IIS configurations, in case Shared configuration is configured in your IIS then normal installation of dotnet hosting bundle package wont work, to make it work you need to install bundle package by command line with the argument as below:

dotnet-hosting-{VERSION}.exe OPT_NO_SHARED_CONFIG_CHECK=1

you can refer ASP.NET Core Module with an IIS Shared Configuration

This solution work for me because we are using the shared configuration in IIS