ASP NET in a Nutshell 2nd Edition-ASP NET in a Nutshell 2nd Edition

11.1 Deploying ASP.NET Applications

For most common applications, all you need to do to deploy the application is set up an IIS virtual directory on the target machine and copy the application's files to it. Assuming that the .NET Framework is installed on the target machine, the application should then run without further configuration or setup.

This type of scenario includes both ASP.NET applications written with their code inline in .aspx files and those that use code-behind files. Note, however, that deploying the code-behind files themselves is not necessary, as long as you deploy the assembly or assemblies compiled from them.

To deploy an ASP.NET application:

Create and configure a new IIS virtual directory (or web site) on the target machine using Internet Services Manager.
Use Windows Explorer, XCOPY, FTP, or another transfer mechanism to copy the files and folders contained in the application's root directory to the new directory on the target machine. If you have Visual Studio .NET, you can also use the Copy Project command from the Project menu to deploy the files to a new location, as described later in this chapter (this does not require step 1, as the Copy Project command will take care of that as well).

As long as any assemblies you're using are in the bin subdirectory of your application and you're not using COM components through COM Interop, it's really that simple. Because all application-specific configuration information is contained in your web.config file(s), this information is automatically copied with the application. In situations when you use shared assemblies, a little more work is necessary, as we'll discuss in the next section.

[ Team LiB ]