Whinge: Windows Application Project templates vs Website Templates

January 6, 2008


I’m sure you’ve all noticed this but the ASP.NET website application template doesn’t let you run the website application and make on the fly code changes, save them and refresh the page and watch it take effect while the website template does. There are a few advantages and disadvantages of both the templates but from my experience the trend with more involved and complex websites the trend is to have an asp.net web application template. This can get tedious when it takes you 1 minute to hit play and build the database project, data layer project, LINQ classes etc and finally the asp.net website, then another 2 minutes of creating some dummy data to get to where you want in the application to finally execute the piece of code for unit testing and bang, it fails because you forgot to check for null, or what ever the case may be. With the Website templates it’s so much easier to just make the changes, hit save, refresh and wallah hey presto you’re done, rather than pressing stop, waiting for another 15 seconds for that to work (this is on a fast laptop mind you, and not even in a virtual pc! native!) then make the changes and hit play and go through it again. 

I hope the asp.net program manager hears this whinge and includes that nice “save and compile per page” feature the website template has and include it into the website application template.


**Updated the next day **






Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: