Build Model of ASP.NET 2.0 (I hate it)

I love ASP.NET 2.0 but what I hate is that when we publish the application it produces million of files (One for each webpage). It create a compiled version of the page and puts it in the bin directory. Now, the problem comes when you have an aspx page on the production and you simply want to change text in the aspx page. In VS.NET 2003 you could simply open the aspx file and change the text in the html view. But if you want to do the same for VS.NET 2005 then you need to compile and publish the whole application after changing the text which really is stupid.

This means even if you spelled something wrong on your page then you have to compile and publish the whole website and upload the whole website again to see your changes.

Another bad thing I noticed is when you do "Find all references" it takes hell lot of time to generate the reference list. Why is everything soo slow in VS.NET 2005???

Posted on Sunday, April 9, 2006 8:15 PM | Back to top

Comments on this post: Build Model of ASP.NET 2.0 (I hate it)

# re: Build Model of ASP.NET 2.0 (I hate it)

If you combine a VS 2005 Web Site Project with a Web Deployment Project, you can produce a single assembly for the site and just update one file on changes.

If you prefer the model of VS 2003, you can use the VS 2005 Web Application Project option. It sounds like this is what you are after. You can learn more about it here: http://weblogs.asp.net/scottgu/archive/2006/04/05/442032.aspx

Hope this helps,

Scott

P.S. Web Application Projects also have much faster "Find all references" support.

Left by scottgu on Apr 09, 2006 8:46 PM