Overview
Unlike the ASP. NET era, ASP. Core is no longer hosted by the IIS worker process (w3wp.exe), but is run with a self-hosted Web server (Kestrel), and IIS is a reverse proxy role forwarding request to an ASP. NET Core program that Kestrel different ports. The received request is then pushed to the middleware pipeline, and the HTTP response data is then written back to IIS after processing your request and related business logic, eventually to different clients (browsers, apps, clients, etc.). While the configuration files and procedures will be slightly adjusted, the most important role in the middle is aspnetcoremodule, which is one of the IIS modules, the request is immediately forwarded to IIS, and quickly redirected to the ASP. So at this point we don't need to set up the application pools to host our code, it is only responsible for forwarding the request.
Before you deploy, make sure that you have Aspnetcoremodule managed modules installed on your IIS, and if not, click here to download and install
Ii. release of the project
Target Framework selects the corresponding Netcore version
Finally add a Web site: application pool Select unmanaged mode
As a brief note:
Detailed reference: https://www.cnblogs.com/wangjieguang/p/core-iis.html
IIS Deployment Net Core