You can choose from a variety of methods for making your Web application available to your users. Your choice may depend on the software available on the production server. The following three methods help you choose what might work best for you.
For any method you use, you need to provide some basic information so that the application is copied to the correct Web server with the correct application name. The information you provide when you copy your Web application to the production server includes the elements of the URL for the Web application.
Typically you can’t specify a server unless it already exists, but you can rename your Web application when you copy it to the server. For example, if you used a code name for your application during development, you can rename the application when you copy it. When deploying, you can use a new name for the application’s URL that is easy for a user to remember.
If your production server has FrontPage Server Extensions installed, you can quickly deploy your application by copying the project. The extensions are provided with Microsoft® Internet Information Server (IIS).
To deploy through FrontPage Server Extensions
Note If you want to use secure transmissions while deploying to the production server, select the Connect using Secured Socket Layer check box.
A new application root is created on the destination Web server and the files in the Web application are copied to that new folder. The name you specified in the Copy Web dialog box becomes part of the application's URL. You can now perform a final verification of the application.
If your production server does not have FrontPage Server Extensions or if your application requires special deployment configurations, you can use Posting Acceptor available with the Visual InterDev Enterprise Edition.
For more a detailed description about deployment mapping and Posting Acceptor, see Deployment of a Web Project.
You might prefer to manually deploy some of your files. Because the detailed steps depend on the tools you actually use, they are not covered here. However, here is a list of tasks you should consider.
For more information about possible deployment tasks, see Solution Building and Packaging Reference.