因无相关文档，请求提供ASP.NET Boilerplate服务在IIS的发布步骤

Hey there! Let me walk you through the detailed steps to get your ASP.NET Boilerplate (ABP) service up and running on an IIS server. I’ve broken this down into clear, actionable steps so you won’t miss anything important.

1. Prerequisites First! #

Before diving in, make sure your server and local setup have these covered:

• IIS installed on your server, with the ASP.NET Core Module enabled (for ASP.NET Core-based ABP projects) or the appropriate ASP.NET features (for traditional .NET Framework ABP projects).
• The matching .NET Runtime (or SDK, if you need to build on the server) installed on the IIS server—check your project’s target framework to pick the right version.
• Your ABP project runs smoothly locally (no build errors, all features work as expected).

2. Publish Your ABP Project Locally #

First, package your project into deployable files:

• Using Visual Studio:
  1. Open your ABP solution, right-click the web project (usually named YourProjectName.Web.Host or YourProjectName.Web.Mvc) and select Publish.
  2. In the Publish window, choose Folder as the target, then specify a local folder (e.g., C:\ABP_Publish) to save the published files.
  3. Make sure the Configuration is set to Release (this optimizes the code for production), then click Publish. Wait for the process to finish.
• Using Command Line:
  If you prefer the terminal, run this command from your web project’s root directory:

  dotnet publish -c Release -o C:\ABP_Publish
  

3. Move Published Files to the IIS Server #

Now get those files onto your server:

• Use FTP, a shared network folder, or Remote Desktop to copy all files from your local publish folder to a directory on the IIS server (e.g., C:\inetpub\wwwroot\YourABPService).
• Important: Make sure the IIS_IUSRS and IUSR user groups have read (and write, if your app needs to upload files or write logs) permissions on this server directory. Right-click the folder → Properties → Security tab to adjust permissions.

4. Create a New Website in IIS #

Let’s set up the website in IIS Manager:

1. Open IIS Manager on the server (search for "IIS" in the Start menu).
2. Right-click the Sites node in the left sidebar and select Add Website.
3. Fill in the details:
   • Site name: Give it a meaningful name (e.g., "ABP_Demo_Service").
   • Physical path: Browse to the server directory where you copied the published files.
   • Binding: Choose an IP address (pick "All Unassigned" if you want it accessible via any server IP), set a port (e.g., 8080—avoid port 80 if another site is using it), and add a host name only if you have a domain pointing to the server.
4. Click OK to create the website.

5. Configure the Application Pool (Critical Step!) #

ABP apps need the right application pool settings to run:

1. In IIS Manager, go to Application Pools in the left sidebar.
2. Find the pool matching your website’s name (it’s created automatically when you add the site), right-click it and select Advanced Settings.
3. Adjust these key settings:
   • .NET CLR Version:
     • For ASP.NET Core ABP projects: Select No Managed Code (since ASP.NET Core runs its own runtime).
     • For .NET Framework ABP projects: Select the matching .NET version (e.g., v4.0).
   • Managed Pipeline Mode: Set to Integrated.
   • Identity: If your app needs access to databases, file shares, or other resources, you can set this to LocalSystem (for broad permissions) or a dedicated service account with the necessary access. The default ApplicationPoolIdentity works for most cases, but double-check permissions if you run into issues.

6. Tweak ABP Configuration for Production #

Don’t forget to update your app’s settings to work on the server:

1. Open the appsettings.json file in your server’s publish directory.
2. Database Connection String: Replace the local connection string with the one pointing to your production database. Make sure the server can reach the database, and the credentials have the right permissions (read/write).
3. AppUrl: Update this to match your IIS site’s binding address (e.g., "AppUrl": "http://your-server-ip:8080").
4. Other Services: If your ABP app uses Redis, RabbitMQ, or external APIs, verify their connection settings are correct for the server environment.

7. Test Your Published Service #

Now let’s make sure everything works:

• On the server, open a browser and visit the site’s URL (e.g., http://localhost:8080).
• Try logging in, navigating through features, and testing any core functionality to ensure nothing breaks.
• If you run into errors: Check the logs folder in your publish directory (ABP logs detailed errors there) or look at IIS’s Event Viewer under Windows Logs → Application for more clues.

8. Common Troubleshooting Tips #

Stuck? Here are quick fixes for common issues:

• 502.5 Error: This usually means the .NET Runtime isn’t installed correctly on the server, or you picked the wrong .NET CLR version in the application pool. Double-check runtime versions and pool settings.
• Database Connection Failures: Confirm the database server allows remote connections, the firewall isn’t blocking the port (default 1433 for SQL Server), and the connection string credentials are correct.
• Permission Denied Errors: Ensure IIS_IUSRS has write access to folders where the app stores logs, uploads, or temporary files.

内容的提问来源于stack exchange，提问作者Vivek Nuna