Development and deployment Web applications ITNET2 Spring 2011 Jesper Rosholm Tørresø

Why take development and deployment into considerations? You should always take D&D into considerations when doing SW/IT development!. But when doing distributed SW/IT development it is even more important. A Web Application is distributed by definition and of course by nature.

The over all picture IDE Host The computer where your integrated development environment is running (Typically your own PC or MAC) Development Host The computer that host the HTTP Server and ASP.NET engine that runs your development version of the web application Deployment Host. The computer that host the HTTP Server and ASP.NET engine that runs your final (custom) version of the web application

Parts to differ between in a webapplication Host with a Web Server/Http Server with – One or more web sites – A web application framework (ASP.NET Java …) A Web application belongs to a website, it has its own URL/URI according to the host at the web site A web application may beside a lot of other items in the site, like static HTML files and other scripts

D&D architecture 1

Or D&D architecture 2

Or D&D architecture 3

Choose a appropriate D&D architecture But remember : Version control Many Developers working at same application parts Division between Design of “User View” and “Application logic”

Processes, rights and likely stuff.

Processes rights and likely stuff. aspnet_wp.exe is no longer used in IIS 6.0 (unless you configure it to run in IIS 5.0 compatibility mode). Instead, ASP.NET applications run inside w3wp.exe processes now. To change the identity of the w3wp.exe process, use the web application pools node in IIS Manager.

Tools VS2008