| title | description | ms.date | ms.topic | helpviewer_keywords | author | ms.author | manager | ms.subservice | monikerRange | |
|---|---|---|---|---|---|---|---|---|---|---|
Publish an ASP.NET web app |
Use the Publish tool in Visual Studio to deploy ASP.NET and ASP.NET Core apps to local web servers like IIS or remote cloud environments like Azure App Service. |
07/15/2024 |
quickstart |
|
ghogen |
ghogen |
mijacobs |
deployment |
>= vs-2019 |
In this article, you'll learn how to publish your first ASP.NET web app to various locations including a local web server such as IIS and a remote cloud environment such as Azure App Service.
This article supports ASP.NET and ASP.NET Core.
Note
This article covers manual deployment, which is great for quickly getting something up and running, but for larger projects and production scenarios, you might want to set up a deployment pipeline. You can use GitHub Actions or Azure DevOps Pipelines to set up automatic deployments with continuous integration for such scenarios.
You need Visual Studio installed with the ASP.NET and web development workload.
If you've already installed Visual Studio:
- Install the latest updates in Visual Studio by selecting Help > Check for Updates.
- Add the workload by selecting Tools > Get Tools and Features.
In Solution Explorer, right-click your project and choose Publish.
If you're publishing this web app for the first time, next you see the Publish wizard.
Note
Visual Studio filters the list of destinations depending on the type of web app.
For detailed steps on publishing your web app, see Quickstart: Deploy an ASP.NET web app.
You can publish your web app as a Docker container to any compatible Docker Container Registry.
Click Next and choose from the available options, such as Azure Container Registry or Docker Hub.
Next, for Azure Container Registry, either select an existing instance or create a new one.
Next, for Docker Hub, provide the publish credentials.
Next, for other Docker container registries, provide the URI and publish credentials.
Next, you see the summary page for the new publish profile that you just created using the Publish wizard. Click Publish and Visual Studio deploys your web app to the specified Docker Container Registry.
Note
The above screenshot is showing a publish profile targeting Azure Docker Registry, but the same Publish button is available for all three Docker Container Registry options.
You can publish your web app to both local and network folders.
First, provide the path and click Finish to complete the Publish wizard.
Next, you see the summary page for the new publish profile that you just created using the Publish wizard. Click Publish and Visual Studio deploys your web app to the provided path.
You can come back to this summary page after you close it. Next time you right-click and choose Publish, Visual Studio opens this summary page. (To get back to the Publish wizard just click New in the summary page.)
You can publish your web app using FTP or FTPS.
Provide the necessary connection details and choose Finish.
Next, you see the summary page for the new publish profile that you just created using the Publish wizard. Click Publish and Visual Studio deploys your web app to the provided FTP or FTPS Server.
You can come back to this summary page after you close it. The next time you right-click and publish, Visual Studio opens this summary page. (To get back to the Publish wizard just click New in the summary page.)
You can publish your web app to IIS if IIS is configured. By default, IIS Express is installed, but you should install the IIS Management tools if you're deploying to IIS from Visual Studio. Note that you don't need to run Visual Studio as Administrator to deploy to IIS Express, only to full IIS.
On the remote web server, install the Web Management Service. Be sure to follow the instructions there to enable remote connections, and make sure the service is started, set up your credentials to remotely administer the web server, and verify them before attempting to deploy. Web Management Service is not required for a local IIS deployment.
On the web server, install IIS 6 Metabase Compatibility. In Windows Settings, under Programs and Features, choose Turn Windows features on or off. Then under Internet Information Services > Web Management Tools, install IIS 6 Management Compatibility. Make sure that IIS Metabase and IIS 6 configuration compatibility are selected.
To configure IIS for ASP.NET Core applications, install the .NET Core Hosting Bundle installer (direct download). For more information, see .NET Core hosting bundle.
If you're working with ASP.NET 4.8 or earlier, or if you need to configure IIS on Windows Server for publishing, you can find detailed steps in Remote debugging ASP.NET on an IIS computer and for ASP.NET Core, Remote debugging ASP.NET Core on an IIS computer.
Warning
A web server must be configured with security best practices in mind. Refer to the IIS documentation for recommended security practices. For IIS 8, see Security Best Practices for IIS 8.
Choose Publish, and then Web Server (IIS).
Pick the desired deployment mode. Choose Web Deploy to immediately deploy the application to the specified server. Choose Web Deploy Package to create a packaged zip file that contains the deployment artifacts for later use by you or someone else.
Provide the necessary connection details and choose Finish. The following screenshot shows a web application published to the default IIS web site (Default Web Site) installed on the local development machine, with a port binding on port 5187. The Destination URL is optional. If not provided, the web site is not automatically launched on publish, and there won't be a link on the Publish screen to access the published site.
The first time you publish, create a username and password. These credentials are specific to WebDeploy deployment. Once they're created, you can't change them in Visual Studio, but you can reset them in IIS. See Sites - Set Credentials dialog box. If you don't have the password, you can download a .publishsettings file, and read it from there. See Import publish settings from IIS.
Warning
Using username and password credentials (basic authentication) is not the most secure method of authentication. Whenever possible, use alternative methods. For example, consider publishing to a package from Visual Studio, and then use WebDeploy.exe from a command line to deploy the package. With that method, you can use IIS Manager to configure authorized Windows users who can publish to the web server, and run WebDeploy.exe under that Windows user account. See Installing and Configuring Web Deploy on IIS 8.0 or Later. If you do use password credentials, be sure to use a strong password, and secure the password from being leaked or shared.
For troubleshooting, see Web Deploy error codes.
Click Browse... to open a Select Package Location dialog box and enter the path to where you want the package to be created, including the .zip file name.
Next, you see the summary page for the new publish profile that you just created using the Publish wizard. Click Publish and Visual Studio deploys your web app to the specified IIS server.
You can import publish settings from IIS and Azure App Service
Manage settings for your web application deployment. By managing settings, you can control the .NET deployment options, as well as behaviors such as how to handle existing files that are not part of the deployment process at the deployment destination. See Manage web deployment settings.