如何将ASP.NET核心应用程序部署到IIS？

安装 ASP.NET Core Hosting Bundle 以确保服务器支持 ASP.NET Core 应用运行，包含 .NET 运行时和 IIS 模块，并通过命令 net stop was /y 和 net start w3svc 重启 IIS；2. 使用 Visual Studio 或 CLI（dotnet publish -c Release -o C:\publish）发布应用，推荐使用框架依赖部署；3. 将发布文件复制到服务器目录（如 C:\inetpub\wwwroot\MyApp），并确保 IIS_IUSRS 具有读取和执行权限；4. 在 IIS 中创建新网站或作为应用程序添加到默认网站，配置站点名称、物理路径和绑定；5. 确保 web.config 文件正确配置 handlers 和 aspNetCore 模块，设置 processPath="dotnet"、arguments=".\YourApp.dll"，并根据需要选择 hostingModel="inprocess" 或 "outofprocess"，若启用 stdoutLogEnabled 则需创建 logs 目录；6. 配置应用程序池，将 .NET CLR 版本设为“无托管代码”，托管管道模式设为“集成”；7. 浏览网站验证部署，若失败则检查事件查看器、启用 stdout 日志、确认 DLL 名称和 Hosting Bundle 安装状态，常见问题包括 502.5 错误（由运行时缺失或参数错误引起）和无效可执行文件错误，建议使用 inprocess 模式提升性能，避免不必要的自包含发布，使用 appsettings.Production.json 管理生产环境配置，最终确保路径、权限和配置一致以完成部署。

Deploying an ASP.NET Core application to IIS involves several steps because ASP.NET Core apps run as standalone processes and are reverse-proxied through IIS using the ASP.NET Core Module. Here’s how to do it properly.

1. Install the ASP.NET Core Hosting Bundle

Before deploying, ensure the target Windows server has the ASP.NET Core Hosting Bundle installed. This bundle includes:

• The .NET Runtime
• The .NET Core Runtime
• The ASP.NET Core Module for IIS

? Download it from the official Microsoft site: //m.sbmmt.com/link/a4cd9bc071c923daab48132b0bb2e4f3 (look under "Hosting Bundle").

After installing, restart IIS by running in Command Prompt (as admin):

net stop was /y
net start w3svc

This ensures the ASP.NET Core Module is properly loaded.

2. Publish the Application

From your development machine, publish the app for deployment:

Using Visual Studio:

• Right-click the project → Publish
• Choose Folder or a custom profile
• Set target framework (e.g., net8.0)
• Set deployment mode: Framework-dependent (recommended unless you need self-contained)
• Click Publish

Using CLI:

dotnet publish -c Release -o C:\publish

This creates a self-contained or framework-dependent output in the specified folder.

3. Copy Files to the Server

Copy the published files (from the publish folder) to a directory on the IIS server, e.g.:

C:\inetpub\wwwroot\MyApp

Ensure IIS has read and execute permissions on this folder. The IIS_IUSRS group should have access.

4. Create an IIS Site or Application

Option A: New Site

• Open IIS Manager
• Right-click Sites → Add Website
• Set:
  • Site name: MyApp
  • Physical path: C:\inetpub\wwwroot\MyApp
  • Binding: e.g., port 80, hostname if needed
• Ensure Start Automatically is checked

Option B: As Application under Default Site

• Expand Default Web Site
• Right-click → Add Application
• Alias: MyApp
• Physical path: same as above

5. Configure web.config (Optional but Important)

The web.config file should be included in the published output. If missing, create one:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <location path="." inheritInChildApplications="false">
    <system.webServer>
      <handlers>
        <add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModuleV2" resourceType="Unspecified" />
      </handlers>
      <aspNetCore processPath="dotnet" 
                  arguments=".\YourApp.dll" 
                  stdoutLogEnabled="false" 
                  stdoutLogFile=".\logs\stdout" 
                  hostingModel="inprocess" />
    </system.webServer>
  </location>
</configuration>

? Use hostingModel="inprocess" for better performance (runs inside IIS worker process), or outofprocess to isolate the .NET Core process.

? Make sure the logs folder exists if stdoutLogEnabled="true" — useful for debugging startup issues.

6. Set Up Application Pool

Ensure the application pool is configured correctly:

• Go to Application Pools
• Find the pool used by your site
• Set .NET CLR Version to No Managed Code
• Set Managed Pipeline Mode to Integrated

ASP.NET Core doesn’t use the legacy ASP.NET pipeline, so "No Managed Code" is correct.

7. Test the Deployment

Browse to your site:

http://yoursite.com

If you see a 500 error or nothing:

• Check Windows Event Viewer → Windows Logs → Application for errors
• Enable stdoutLogEnabled="true" and check the logs folder
• Verify the app DLL name in web.config matches your published .dll
• Confirm the Hosting Bundle is installed and IIS restarted

Common Issues & Tips

• ❌ "The specified executable is not a valid application": Usually means the Hosting Bundle isn’t installed or the app isn’t published correctly.
• ❌ 502.5 Process Failure: Often due to missing runtime or incorrect arguments in web.config.
• ✅ Use inprocess hosting for better performance unless you need isolation.
• ✅ Avoid publishing with self-contained unless necessary — it increases size.
• ✅ Use appsettings.Production.json to manage environment-specific settings.

That’s it. Once the Hosting Bundle is in place and the app is published correctly, IIS will proxy requests to your ASP.NET Core app via the ASP.NET Core Module. Just make sure file permissions, paths, and configuration align.

以上是如何将ASP.NET核心应用程序部署到IIS？的详细内容。更多信息请关注PHP中文网其他相关文章！