5. On the **Connection** tab, you can change the publishing target path from the default *..\\..\\artifacts\\bin\\WebApp9\\Release\\Publish* folder. Click **Next**.
6. On the **Settings** tab, you can select the configuration, target DNX version, and publish options. Click **Next**.
#. Navigate to the publish folder (*..\\..\\artifacts\\bin\\WebApp9\\Release\\Publish folder* in this sample).
#. Copy the **approot** and **wwwroot** directories to the target IIS server. Note: MSDeploy is the recommended mechanism for deployment, but you can use Xcopy, Robocopy or another approach.
#. In IIS Manager, create a new web site and set the physical path to **wwwroot**. You can click on **Browse *.80(http)** to see your deployed app in the browser. Note: The HTTP Platform Handler currently requires `this work-around <https://github.com/aspnet/Hosting/issues/416>`_ to support apps. If you get an HTTP error, see `IIS server configuration`_.
1. Enable the **Web Server (IIS)** server role. In client operating systems (Windows 7 through Windows 10) select **Control Panel > Programs > Programs and Features > Turn Windows features on or off**, and then select **Internet Information Services**.
..image:: pubIIS/_static/rs.png
2. On the **Role Services** step, remove any items you don't need. The defaults are shown below.
..image:: pubIIS/_static/role-services.png
3. Unlock the configuration section.
- Launch IIS Manager and select the server in the **Connections** pane on the left (see image below).
- Double-click **Connection Editor**.
- In the **Section** drop-down, select **system.webServer/handlers**, and then click **Unlock Section**.
..image:: pubIIS/_static/config-edit.png
..image:: pubIIS/_static/unlock.png
- Set the application pool to **No Managed Code**. ASP.NET 5 runs in a separate process and manages the runtime.
The following is not a complete list of errors. Should you encounter an error not listed here, please leave a detailed error message in the DISQUS section below along with the reason for the error and how you fixed it.
- HTTP 500.19 : ** This configuration section cannot be used at this path.**
- You haven't enabled the proper roles. See `IIS server configuration`_.
- HTTP 500.19 : The requested page cannot be accessed because the related configuration data for the page is invalid.
- You haven't installed the correct HTTP Platform Handler. See `Install the HTTP Platform Handler`_
- The *wwwroot* folder doesn't have the correct permissions. See `IIS server configuration`_.
- The IIS 7.0 CoreWebEngine and W3SVC features must be installed to use the Microsoft HTTP Platform Handler 1.x.
- Enable IIS; see `IIS server configuration`_.
- HTTP 502.3 Bad Gateway
- - You haven't installed the correct HTTP Platform Handler. See `Install the HTTP Platform Handler`_
- HTTP 500.21 Internal Server Error.
- No module installed. See `IIS server configuration`_.