| Deployment and Packaging of ASP.Net Application |
| |
| Deployment in ASP.NET 2.0 |
| |
| Now you know that deployment is the process of taking the application and installing it in on another machine, usually by the use of a setup application. Compilation in ASP.NET 2.0 is accomplished by running the new ASPNET_COMPILER.EXE against a Web application. The compiler has many options to compile your projects which include in-place compilation which requires source code distribution, pre-compiled compilation into all binary code, and partial compilation which compiles your user code, but lets you distribute and modify the ASPX markup pages. There are at least 20 different compilation combinations and none of them are likely to be exactly what you probably would hope for - most combinations produce non-repeatable installs and none of the stock combinations create a single deployable assembly that most developers would expect from a pre-compiled application. |
| |
| Deployment with stock projects only is complicated unless you do an in-place deployment. In-place deployment is simple to understand â you simply copy your entire development environment including source code to the server. All the other options require multiple steps of deleting of files and then re-copying files which disrupts application uptime on the server and requires a fairly strict deployment regimen to work reliably. |
| |
|
| |
