JavaScript Editor jscript editor     Web designer 

Main Page

Deploying ASP.NET applications is very straightforward. You need to copy the application files you have created from your development computer to the production Web server that will host your application. You can use the XCOPY command-line tool or your preferred FTP application to copy the files from one location to another. For more information about general deployment, see .NET Framework Deployment Basics.


As an alternative to using the XCOPY command-line tool, which is supported by all versions of the .NET Framework, you can use the new .NET FrameworkВ 2.0 tool located at %SystemRoot%\Microsoft.NET\Framework\version 2 or later\Aspnet_compiler.exe to compile and deploy your Web application. For more information, see ASP.NET Compilation Tool (Aspnet_compiler.exe).

Assemblies that you want to share across Web applications, such as assemblies that contain custom ASP.NET server controls, should be deployed to the global assembly cache (GAC) on a remote server.

If you deploy an application that contains a reference to a custom component registered in the global assembly cache on the local server, the component will not be deployed with the application to the remote server. You will need to install the component in the global assembly cache on the remote server, or you can copy the custom component to the Bin folder of the local Web application before deployment.

For more information, see Global Assembly Cache. For more information about assemblies, see Programming with Assemblies.

Some development tools such as Visual Web Developer have tools that make it easy to deploy your applications.

Expand imagePrerequisites

Expand imagePreparation

Expand imageTo deploy an ASP.NET Web application using XCOPY from the command line

Expand imageTo deploy or update individual files in an ASP.NET Web application from the command line

Expand imageSee Also

JavaScript Editor jscript editor     Web designer