Compilation and Deployment in ASP.NET 2.0 Article posted

September 28, 2006 • from Maui, Hawaii • 11 comments

On this page:

I’ve posted a new looong article on Compilation and Deployment with ASP.NET 2.0 in the Articles section of the site. This article also ran in CoDe magazine this month:

Compilation and Deployment in ASP.NET 2.0

Compilation and deployment in ASP.NET 2.0 has brought some of the biggest changes to the ASP.NET development model. As developers we use page compilation all day long and deployment is something we all have to worry about sooner or later. A lot has changed in both areas and they can affect how you build and deploy your applications so understanding how the model works is crucial. In this article I'll provide a detailed discussion of how compilation and deployment works. I'll also talk about the new Web Deployment Projects and Web Application Projects add-ins that Microsoft is providing to ease some of the pain points of the stock functionality shipped with ASP.NET 2.0 and Visual Studio 2005.

This entry is a placeholder link to allow comments and questions. For longer or more detailed discussions I suggest posting a question on our Message Board.

The Voices of Reason

Mike
September 28, 2006

# re: Compilation and Deployment in ASP.NET 2.0 Article posted

thanks so much for the article I was just about to convert to a WAP project and this was timely.

Hakan
September 28, 2006

# well done

--
great article, a must read for anyone doing asp.net development - Scott G should mention this on his blogs
thanks for all the effort & time you must have put into figuring this out and preparing a 'digested' understandable version
it seems the deployment of stock projects without WDP add-in is indeed a complete writeoff - makes you wonder - what were they thinking ?
--

Andreas Kraus
September 29, 2006

# re: Compilation and Deployment in ASP.NET 2.0 Article posted

Very good article. I fully agree with the .NET 2 Deployment Nightmare.

Clemente Vásquez C.
November 02, 2006

# re: Compilation and Deployment in ASP.NET 2.0 Article posted

Rick Strahl: a very good article !!!!.

keith patton
November 16, 2006

# re: Compilation and Deployment in ASP.NET 2.0 Article posted

brilliant article, probably the best on the web for covering the various options, great stuff.

We are currently using WDP with the stock option, because of the speed advantages when working on the web layer.

Kenan Avdic
December 18, 2006

# re: Compilation and Deployment in ASP.NET 2.0 Article posted

Thank you for the very thorough yet practical article. This is a must-read for any professional ASP.NET 2.0 developer. To signify the importance of the Web Application Projects, Microsoft has included support for WAP in the recently released SP1 for Visual Studio 2005.

Sumanth
July 06, 2007

# re: Compilation and Deployment in ASP.NET 2.0 Article posted

Rick,

Thanks a lot for the fantastic article. Is it correct to say that, technically, CodeBeside is just CodeBehind broken up into two partial classes, or is there more to it than that?

Thanks.

Rick Strahl
July 06, 2007

# re: Compilation and Deployment in ASP.NET 2.0 Article posted

It's similar but not the same. Remember you still get ASP.NET 2.0 and it will still compile standalone and CodeFile pages even if you're using WAP. All WAP does is provide different (uh, better <g>) design time support.

But yeah, it's based on the same concept as CodeBehind in ASP.NET 1.1 one, meaning only codebehind code is compiled into a single assembly.

William Buddle
June 09, 2008

# re: Compilation and Deployment in ASP.NET 2.0 Article posted

I really enjoyed your article. It is excellent.
Writing software in Hawaii, that sounds like heaven.

Thanks.

Tom Pester
February 06, 2010

# re: Compilation and Deployment in ASP.NET 2.0 Article posted

Yes !! I finaly made it to the end of this article. Great job at explaining this mess of options.

Thanks for your time Rik, its realy appreciated

Tom

Tom
March 12, 2010

# re: Compilation and Deployment in ASP.NET 2.0 Article posted

Thank you so much for this article. Was exactly what I needed to understand the mechanics of the compilation system; Microsoft seem to not be interested in explaining it!

Rick Strahl's Weblog