Freshness update: publish-to-iis (#36789)

* Initial plan

* Freshness update: publish-to-iis article

Co-authored-by: wadepickett <10985336+wadepickett@users.noreply.github.com>

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: wadepickett <10985336+wadepickett@users.noreply.github.com>

Author: Copilot

aspnetcore/tutorials/publish-to-iis.md

@@ -1,16 +1,17 @@
 ---
 title: Publish an ASP.NET Core app to IIS
+ai-usage: ai-assisted
 author: wadepickett
 description: Learn how to host an ASP.NET Core app on an IIS server.
-monikerRange: '>= aspnetcore-2.1'
+monikerRange: '>= aspnetcore-8.0'
 ms.author: wpickett
 ms.custom: mvc
-ms.date: 10/03/2019
+ms.date: 02/23/2026
 uid: tutorials/publish-to-iis
 ---
 # Publish an ASP.NET Core app to IIS
 
-This tutorial shows how to host an ASP.NET Core app on an IIS server.
+Internet Information Services (IIS) is a flexible, general-purpose web server that runs on Windows and can host ASP.NET Core apps. IIS is a good choice when you need to run ASP.NET Core apps on Windows Server in an on-premises or hybrid environment, need Windows Authentication, or require integration with other IIS features such as URL Rewrite, Application Request Routing, or centralized certificate management.
 
 This tutorial covers the following subjects:
 
@@ -37,6 +38,8 @@ This tutorial covers the following subjects:
 
 Install the *.NET Hosting Bundle* on the IIS server. The bundle installs the .NET Runtime, .NET Library, and the [ASP.NET Core Module](xref:host-and-deploy/aspnet-core-module). The module allows ASP.NET Core apps to run behind IIS.
 
+ASP.NET Core apps hosted in IIS use the *in-process hosting model* by default (since ASP.NET Core 3.0). In-process hosting runs the app in the same process as the IIS worker process (`w3wp.exe`), which provides better performance than out-of-process hosting. For more information, see <xref:host-and-deploy/iis/index>.
+
 Download the installer using the following link:
 
 [Current .NET Hosting Bundle installer (direct download)](https://dotnet.microsoft.com/permalink/dotnetcore-current-windows-runtime-bundle-installer)
@@ -74,14 +77,18 @@ Create any type of ASP.NET Core server-based app.
 * The app is published to a folder.
 * The folder's contents are moved to the IIS site's folder (the **Physical path** to the site in IIS Manager).
 
+ASP.NET Core apps can be published as *framework-dependent* (the server must have .NET installed) or *self-contained* (includes the .NET runtime in the published output). For most IIS deployments, the framework-dependent approach is recommended because the .NET Hosting Bundle provides the required runtime on the server. For more information, see [.NET application deployment](/dotnet/core/deploying/).
+
+A `web.config` file is generated automatically when the app is published. IIS uses this file to configure the ASP.NET Core Module for the app. Don't remove or manually edit the `web.config` file unless you're making advanced configuration changes.
+
 # [Visual Studio](#tab/visual-studio)
 
 1. Right-click on the project in **Solution Explorer** and select **Publish**.
-1. In the **Pick a publish target** dialog, select the **Folder** publish option.
-1. Set the **Folder or File Share** path.
+1. In the **Publish** dialog, select **Folder** as the publish target and select **Next**.
+1. Set the **Folder location** path.
    * If you created a folder for the IIS site that's available on the development machine as a network share, provide the path to the share. The current user must have write access to publish to the share.
-   * If you're unable to deploy directly to the IIS site folder on the IIS server, publish to a folder on removable media and physically move the published app to the IIS site folder on the server, which is the site's **Physical path** in IIS Manager. Move the contents of the `bin/Release/{TARGET FRAMEWORK}/publish` folder to the IIS site folder on the server, which is the site's **Physical path** in IIS Manager.
-1. Select the **Publish** button.
+   * If you're unable to deploy directly to the IIS site folder on the IIS server, publish to a folder on removable media and physically move the published app to the IIS site folder on the server, which is the site's **Physical path** in IIS Manager. Move the contents of the `bin/Release/{TARGET FRAMEWORK}/publish` folder (where `{TARGET FRAMEWORK}` is the target framework moniker, for example `net10.0`) to the IIS site folder on the server, which is the site's **Physical path** in IIS Manager.
+1. Select **Finish** and then select **Publish**.
 
 # [.NET CLI](#tab/net-cli)
 
@@ -91,7 +98,7 @@ Create any type of ASP.NET Core server-based app.
    dotnet publish --configuration Release
    ```
 
-1. Move the contents of the `bin/Release/{TARGET FRAMEWORK}/publish` folder to the IIS site folder on the server, which is the site's **Physical path** in IIS Manager.
+1. Move the contents of the `bin/Release/{TARGET FRAMEWORK}/publish` folder (where `{TARGET FRAMEWORK}` is the target framework moniker, for example `net10.0`) to the IIS site folder on the server, which is the site's **Physical path** in IIS Manager.
 
 ---
 
@@ -144,9 +151,6 @@ To learn more about hosting ASP.NET Core apps on IIS, see the IIS Overview artic
 * [IIS documentation](/iis)
 * [Getting Started with the IIS Manager in IIS](/iis/get-started/getting-started-with-iis/getting-started-with-the-iis-manager-in-iis-7-and-iis-8)
 * [.NET application deployment](/dotnet/core/deploying/)
-* <xref:host-and-deploy/aspnet-core-module>
-* <xref:host-and-deploy/directory-structure>
 * <xref:host-and-deploy/iis/modules>
-* <xref:test/troubleshoot-azure-iis>
 * <xref:host-and-deploy/azure-iis-errors-reference>
 * [Sticky sessions with Application Request Routing](/iis/extensions/configuring-application-request-routing-arr/http-load-balancing-using-application-request-routing)