February CTP Released: Web Application Projects & Web Deployment Projects


I’m excited to announce the latest refresh (February CTP) to both Web Application Projects and Web Deployment Projects!  Details below, feedback wanted as always! 


Web Application Projects
Updated Feb 10, 2006
Visual Studio 2005 Web Application Projects provide a companion web project model option for Visual Studio 2005 that works like the Visual Studio .NET 2003 web project model and can be used as an alternative to the built-in web-site based version. This latest release adds designer field generation and migration support.
» Download Web Application Projects


Web Deployment Projects
Updated Feb 10, 2006
If you have a complex Visual Studio 2005 web project which requires different web.config settings for deployment or you’d like more control over the compilation process, check out Web Deployment Projects, a new tool for Visual Studio 2005. This latest version adds support for Web Application Projects, preserves file encoding when using the new merge tool, and more.
» Download Web Deployment Projects

Comments (5)

  1. themaisite says:

    Would like to have all ASP.NET blog link to my site

  2. Brian,

    With regard to,

    "Visual Studio 2005 Web Application Projects provide a companion web project model option for Visual Studio 2005 that works like the Visual Studio .NET 2003 web project model and can be used as an alternative to the built-in web-site based version."

    What are the pro’s and con’s of using these two approaches?  It seems that the Web App Projects model makes it easier to upgrade in some cases.  But beyond that, are there compelling reasons to use this model?  Do projects load faster or execute faster using one model as opposed to another?  Scalability?  It seems that having all code files within the project compiling into a single assembly might not scale as well or load as fast as the other model.  

    Thanks in advance for any insights or links to articles where this is covered.

    Barry Wadsworth

  3. bgold says:

    Barry:

    There isn’t any measurable runtime performance difference between the two models.  Also, there are clear pros and cons in terms of development model between the two.  For some development teams and developer workflows one is going to be better than the other, and vice-versa.  I don’t have a lot of details other than that.  One of the things we are working on over the next few months is producing whitepapers and guidance that better articulate the differences between the two models and which is going to be the best route for different scenarios and use cases.  It certainly won’t be if you are blue, do this and if you are green do that, but giving people the depth of context and information they need to make educated and informed decisions.

    Sometimes the technology runs ahead of the guidance (I think that is more then sometimes!) — Hope this helps a little bit.

    Thanks,

    Brian

    on these differences and which is best for different scenarios.

Skip to main content