These options will be used regardless of whether you publish with Web Deploy or a different publishing method. Packages are configuration specific and settings are per configuration, so you need to choose the configuration and configure the setting before creating a package.Ĭonfigure Items to deploy (applies to all deployment methods) In Solution Explorer, expand the ContosoUniversity node and double click Properties (C#)Ĭhoose the Configuration for the package. Start Visual Studio 2010 and load up the Contoso University C# solution.
Both of these methods will generate 1) a standard Web Deploy package and 2) a batch (.cmd) file that will help you deploy the package.
In Visual Studio 2010, you can create Web Deploy packages through the UI or by using MSBuild on the command line. In this tutorial, we will deploy the package to our server from the development computer and we will also explore importing it on the server using Web Deploy UI in IIS Manager. A package contains the files (binaries and static content), databases, and IIS settings that you want to deploy. In this walkthrough, we will learn how developers can create Web Deploy packages, which can be deployed by users who have access to the web server (such as administrators, or IT / ops teams). So far, we have installed Web Deploy on a web server and enabled non-administrators to deploy applications to IIS 7.