When deploying ASP.NET Core applications to IIS, you need to pay attention to the following key points: 1. Install the .NET Core runtime and Hosting Bundle, otherwise it will cause HTTP 500 errors; 2. Make sure to include web.config when publishing applications and select the appropriate publishing mode; 3. Configure the IIS site and application pool, set "unmanaged code" and correct permissions; 4. Check the logs when there is a problem and manually test the Kestrel startup situation.

Deploying ASP.NET Core to an IIS environment is not difficult, but there are several key points that must be paid attention to. IIS itself cannot run .NET Core applications directly, but forwards the request to the built-in server of Kestrel through reverse proxy. Therefore, the entire process needs to configure the cooperation between IIS and .NET Core.

Install the necessary runtime and managed components

Before you begin, make sure that the target server has the correct .NET Core runtime and IIS managed bundles installed. Many people miss the hosting bundle, which will cause the application to not function properly.

• If you are using .NET Core 3.1 or later, you need to download and install the corresponding .NET Runtime and Hosting Bundle.
• Hosting Bundle will automatically install IIS modules (such as AspNetCoreModuleV2) and configure pipeline mode.
• How to check whether the installation is successful: Enter dotnet --info on the command line to see if the SDK and runtime information are listed.

If these components are not installed correctly, you will not start even if you publish the program and you will usually see HTTP errors 500.0 or 500.30.

Publish and deploy application files

The most common way to publish an ASP.NET Core application is to use Visual Studio or CLI tools to generate self-contained or dependent framework publishing packages.

• If you use Visual Studio, right-click the project and select "Publish", then select "Folder" or Remote FTP, etc.
• If you choose a framework-dependent publishing mode, the corresponding .NET runtime must be installed on the server; if you do not want to rely on the environment, you can choose self-contained mode, but the size will be larger.
• After the release is completed, copy the file to the target directory on the server, such as C:\inetpub\wwwroot\myapp .

Be careful not to miss the web.config file, which contains the path and startup parameters to the .NET Core runtime. If this file is missing or is configured incorrectly, IIS will not know how to deal with your application.

Configuring IIS Sites and Application Pools

The next step is to create a site or application in IIS and set up an application pool.

• Create a new site, bind a port or domain name, and the home directory points to the folder you posted.
• It is recommended to create one separately and set .NET CLR 版本to "No Managed Code" because Kestrel is a native process.
• Also make sure the "Enable 32-bit Application" of the application pool is set to false unless you have special needs.

If your application crashes during operation or fails to start, you can view the log file. By default, the stdout log will be generated in logs folder in your application directory. Remember to enable logging function in web.config :

 <aspNetCore processPath="dotnet" arguments=".\YourApp.dll" stdoutLogEnabled="true" stdoutLogFile=".\logs\stdout" />

Handle FAQs and permission settings

The most common problems during the deployment process include insufficient permissions, path errors, port conflicts, etc.

• Make sure that the IIS user (usually IIS_IUSRS ) has read and write permissions to your application directory, especially if you use local logs or cached files.
• Check that Kestrel is started correctly. You can manually run dotnet YourApp.dll on the server to see if there is any error.
• If you enable HTTPS in your development environment but do not configure the certificate on IIS, it may cause a redirect error. At this time, you can temporarily turn off HTTPS and force jump.

In addition, sometimes the application is not a problem to start, but it returns 500 or blank pages when accessing. You must read the log at this time. ASP.NET Core will not expose detailed error information by default unless you enable development mode.

Basically that's it. As long as you follow the steps step by step, you can deploy it smoothly in most cases.

The above is the detailed content of Deploying ASP.NET Core Applications to an IIS Environment. For more information, please follow other related articles on the PHP Chinese website!