VS 2005 Web Application Project Release Candidate Now Available

May 8th Update: The final release of the VS 2005 Web Application Project is now live.  You can learn more about it here.

Today we published the Release Candidate of the VS 2005 Web Application Project on the web.  You can download it now from here. 


Over the next few days we’ll be updating the in-depth tutorials on how to use it on http://webproject.scottgu.com.  We have also posted a whitepaper that describes the project option more (and when to use it versus a VS 2005 Web Site Project) hereYou can also read more about the original motivation for adding the VS 2005 Web Application Project option here.


There is also a new forum on http://forums.asp.net that is dedicated to VS 2005 Web Application Project questions.  You can access it here.


What is new with today’s release?


Today’s release is a major refresh that provides a ton of new functionality and rounds out the feature-set.  Some of the major new features added since the February preview:

  • Event handler generation and wire-up from the WYSIWYG designer    
  • F7/Shift-F7 Navigation Support (switch between page views)
  • Add New Item Wizard to add pages based on Master Pages (easily pick master)
  • Richer Publishing Support
  • Connection String and Settings Support in Web.Config
  • Resources and .Resx Resource Editor Support
  • Support for building multi-project applications and sub-web projects
  • .ASPX files no longer locked when debugging
  • Support for root-path based image and stylesheets (/images/foo.jpg)
  • Control Registrations within Web.Config files
  • Web Service Cross-Project Reference Support
  • Section 508 and WCAG Accessibility Checker Support
  • Ability to create an IIS Vroot/Application setting within Project Dialog
  • SQL DataSource Control Support
  • ASP.NET Custom Folder Templates
  • Component Designer Support
  • Support to Drag/Drop User Controls, StyleSheets, Images from Solution Explorer to designer
  • New Web Service Project Template
  • SQL Express Support

Also included in this build is support to automatically migrate a VS 2003 Web Application to be a VS 2005 Web Application Project.  With the VS 2005 Web Application Project installed, you can now simply do a File->Open File within VS 2005 and select a VS 2003 .sln or  project file to kick off a migration wizard that will convert the project to be VS 2005 Web Application Project (no need to open or modify any project file settings manually anymore). 


This will provide a straight-forward way to migrate a VS 2003 Web Application to VS 2005 without having to-do much work (because this new project type uses the same compile and project semantics as VS 2003 you shouldn’t need to make code changes to get a VS 2003 app building and running in VS 2005 – we’ll be posting a detailed step-by-step tutorial on how to-do this shortly). 


We also have added automated migration support to help take a VS 2005 Web Site Project and migrate it to the VS 2005 Web Application Project option you can do that too (we’ll also be publishing tutorials on this as well).


If you have installed and used the previous two preview releases of the VS 2005 Web Application Project, you can simply uninstall the previous installs and install this new one.  The project file format and code is the same, so your apps will keep working (but now with more features to use).


Quick Step-By-Step Walkthrough


To get a quick sense of how VS 2005 Web Application Projects work, you can install it and try out the simple “hello world” walkthrough below:


Step 1: Create a New VS 2005 Web Application Project


Choose the File->New Project menu item and select the “ASP.NET Web Application” project template (note below that we also now have an ASP.NET Web Service project template if you are building a web service project).



This will create a project that contains a default.aspx page (along with associated code-behind file, and a .designer.cs/.vb file where control field declarations and tool-generated code is persisted):



Note that I didn’t have to associate this project with an IIS application.  Unlike VS 2003, I don’t need to have IIS on the machine – instead developers can use the built-in VS web-server if they want to instead.  Alternatively, they can open up the project properties to map (or create) an IIS application to handle the project (see step 5 below on how to-do this). 


Step 2: Open and Edit the Default.aspx Page


Double click on the default.aspx page node in the solution explorer to open and edit it (note: you can now use F7 and Shift-F7 to toggle between the designer, .aspx source, and code-behind views of the page).  Add a button and label to the page:



This generates .aspx markup source like so:


<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="Default.aspx.cs" Inherits="WebApplication4._Default" %>


<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">


<html xmlns="http://www.w3.org/1999/xhtml" >

<head runat="server">

    <title>Untitled Page</title>



    <form id="form1" runat="server">



        <asp:Button ID="Button1" runat="server" Text="Push Me!" />


        <br />

        <br />


        <asp:Label ID="Label1" runat="server"></asp:Label>







Within the WYSIWYG designer, double click on the button control to generate a “Click” event handler.  This will automatically generate the appropriate event-handler in your code-behind and wire it up to the control. Within your code-behind file you can then write your code to work against the controls on the page:


using System;

using System.Data;

using System.Configuration;

using System.Collections;

using System.Web;

using System.Web.Security;

using System.Web.UI;

using System.Web.UI.WebControls;

using System.Web.UI.WebControls.WebParts;

using System.Web.UI.HtmlControls;


namespace WebApplication4


    public partial class _Default : System.Web.UI.Page


        protected void Button1_Click(object sender, EventArgs e)


            Label1.Text = "Built using the VS 2005 Web Application Project!";





The code above is actually the exact same code-behind code that you would write with a VS 2005 Web Site Project based application.  The difference is that with a VS 2005 Web Site Project the control declarations are dynamically generated by the project at compile time (rather than persisted in the project) within a partial class that is compiled together with the code-behind file.  With VS 2005 Web Application Projects each page instead has a .designer.cs file (or with VB projects .designer.vb file) that contains the persisted control declarations within a partial class.  This is updated by VS anytime you modify the .aspx page.  For example, the Default.aspx.designer.cs file for our above sample would look like this:


namespace WebApplication4 {


    public partial class _Default {

        protected System.Web.UI.HtmlControls.HtmlForm form1;

        protected System.Web.UI.WebControls.Button Button1;

        protected System.Web.UI.WebControls.Label Label1;




Persisting these declarations within .designer.cs files within the project allows very fast compile times (in general people in the beta program have found VS 2005 Web Applications compile 10-15% faster than VS 2003 Web Projects, and much, much faster than VS 2005 Web Site Projects when a full build/re-build scenario occurs).  It also allows any class within the project (or a separate project that references your web project) to directly reference and use a page and its controls if you want to.  It also makes code refactoring very fast even for very large projects.


If you want, you can also optionally declare your controls manually within your code-behind file (for example: if you wanted to add a custom attribute to them or define a custom type to use).  If VS detects that a control declaration has already been made in the code-behind file by you, then it will automatically omit duplicating it from the .designer.cs/.vb file (which is a nice, useful feature).


Step 3: Build the Project


When you build the web-site, all code and pages within the project will be compiled into a single project assembly (like VS 2003 did).  This assembly will be persisted in the \bin directory of the web project.  You can see this by doing a build, and then clicking the “Show All Files” solution explorer icon to see files on disk that are not part of the project:



Note that only files and directories specifically added to a VS 2005 Web Application Project file get added to the application and project view.  This makes it easy to have files on disk underneath a web project root and not have them show up in the solution explorer or be included in a build or publish step.


Step 4: Run the Project


Set a breakpoint on the button click event handler, and then hit F5 to run the application.  Because we haven’t yet associated this project with an IIS application, it will by default launch the built-in VS web-server to run it:



I can then obviously hit breakpoints and debug the application:



Step 5: Customize Project Properties


Double-click on the “Properties” node in the Solution Explorer to bring up the project properties window.  This provides the same options as standard VS 2005 class libraries and Windows Forms projects (for example: assembly name, versioning, code signing, code analysis, resources, etc).  It also then adds an additional “Web” property tab for web-specific settings:



Within this tab you can customize a bunch of launch options for the project, as well as control whether it uses the built-in VS web-server or IIS to run the application (note: all settings are persisted in the project’s .csproj or .vbproj file).


To map the application to use IIS instead, you can either use the IIS admin tool to create your application to point to your directory, or with this new VS 2005 Web Application Release simply specify a new virtual directory/application to create and click the “Create virtual directory” button within the “web” property tab.  This will create and associate it for you automatically with IIS.


For example, in the above properties dialog I chose to map the application to a new http://localhost/WebApplication4/ IIS application.  I clicked the “Create virtual directory” button to setup this mapping to my new project.  And now when I next run the application it will use IIS:



Step 6: Publishing the Project


To publish a VS 2005 Web Application to a remote server (or just another directory on your local system), select the Build->Publish menu item.  This brings up a publish dialog that provides support for many new publishing options:



If you click on the “…” button in the publish dialog you can configure the publish location path you want to use.  VS 2005 Web Application Projects support several options:



File System – Deploy the application to a local or remote UNC share

IIS – Deploy the application to a local IIS web application

FTP – Deploy the application to a FTP based location

Remote Site – Deploy using FrontPage Server Extensions over HTTP to a local or remote server (also includes the ability to create a new remote site using FPSE)


VS 2005 Web Applications also support multiple file deploy modes – including both clean replacement (where the target directory is deleted and then recreated) as well as incremental copies (where only modified files are copied over).  The incremental approach is ideal for cases where you only make a change to 1 or more pages, and simply want to copy the changed .aspx files and single .dll assembly.


For more advanced deployment options, you can also optionally associate a VS 2005 Web Deployment Project with a VS 2005 Web Application Project (VS 2005 Web Deployment Projects work with both Web Site and Web Application Projects).  We will be shipping the final released build of the VS 2005 Web Deployment Project download in a few days. 


Next Steps


We’ve had about 150 private beta testers who have been testing out VS 2005 Web Application Project builds the last few months, and have provided great feedback on features to add and bugs to fix.  Their feedback has been invaluable and has really helped shape the feature-set and direction of the project.


We are calling this week’s download a “Release Candidate” because we expect to see a few last minute feature requests and bug reports once thousands more people start using it.  Our plan is to spend the rest of this month responding to these, and then publish the final build on the web.  We are then working to also add VS 2005 Web Application Support directly into VS 2005 SP1 (but we wanted to make it available as a web download now before then). 


I’ve received a few questions from people about our web project model plans going forward.  To quickly summarize a few of the common answers:


-- We will be fully supporting both the VS 2005 Web Site and VS 2005 Web Application Project Model going forward.  Both will be fully supported in the next release of Visual Studio.  So both are “safe” bets to use going forward to build new projects.


-- Deciding which project model option to use really depends on your particular preference in terms of development style, your team dynamics, and the size and requirements of the project.  There is no “right” or “wrong” project option to use (just like language preferences, while people might be passionate about a particular choice, it really depends on you and your background as to which is better for your scenario).  We have published an initial whitepaper here that provides guidance on the scenarios and the pros/cons of each model to help you decide.


-- This new project option isn’t just about making upgrades of large VS 2003 Web Projects easier.  It is also ideal for a lot of new projects that have rich enterprise scenarios/requirements.


Hope this helps,




  • Wow great! I was actually reading &quot;Upcoming ASP.NET Releases in April&quot; at this same page and wondering if I should continue to work with the preview install or hold off and wait for this. Then I refreshed the page and wham! Great timing for me, thanks!

  • Excellent! One question though. We currently have C# &quot;Library&quot; projects that have web user controls in them. We use them to create user controls are plugged into a seperate web application (which is a regular asp.net web application project).

    It's great that we can convert a web application project from VS2003 to VS2005, but can we easily convert a VS2003 Library project into a VS2005 Web Application project? Because that is what we would have to do for these ASCX-containing library projects (for the record, they aren't web projects, because we test/deploy them in the other web application, so making them a web project just caused problems).

  • Waiting for RTM...

    Thank you, guys!

  • I am using Chinese version VS2005, I can't install &quot;Microsoft Visual Studio 2005 – Update to Support Web Application Projects&quot; . Is it only for English version? So sad I can't use the lasted Web Application Project.

  • So I'm still a little confused between the this new Web Application Project RC and the existing Web Site Project template in VS2005. Is there a link to some resource explaining which one to use. Does this work with Atlas? Which one should I be using if I am building a new web site?



  • Is there a way to auto convert a 2005 Web Site Project to a 2005 Web Application Project?

  • I just read that you can. Sorry for asking :)

  • Cool!

    In my solution, i have web application project; referencing &quot;user control project&quot; which is refernecing a &quot;library project&quot; which has reference to other libaries like enterprise library. I am using WAP-CTP; the problem is; the library project and its referenced libaries doesnt appear in web application's &quot;bin&quot; folder; i have to copy them manually (written copy statements in user control project's post build events; along with copying ascx files to web-app)

    Will try this RC; and update you if that problem is still unresolved.

  • Scott I have been using the Web Aplications B2 and Web Deployments B2 projects together on a ported VS2003 project. When running the Web Deployment build, the code behind asembly for the Web Application project is not compiled in to the Web Deployment single assembly. Is this option going to be available at any point?

  • Scott,

    THANKS!!! I am very very glad that you guys are building this option for us and that it will be baked into future released of VS.NET (and supported)!

    The project I'm on had zero chance of migrating to ASP.NET 2.0 with the Web Site Project semantics. It would've been a 600+ screen application restructure to migrate... and that would've been a long way's out. This should enable us to migrate much much sooner.

    Thanks again,

    Jeff Handley

  • I sent you an email at devconnections and you said Omar was working on a whitepaper. Wholla, it's been published and the Release Candidate of WAP made available two days later. You guys are great! The whitepaper clears us my confusion on when to use the WAP or WSM model.


  • w00t. You rock!

  • Hi Dave,

    Yep -- you can convert VS 2003 class library projects to be VS 2005 Web Application Projects too. Probably the easiest way is to migrate them to be VS 2005 class library projects, and then open up their project files and change the projectype GUID to match the one you see when you create a new web application project. Then, when you open up the project again, the project type will be a VS 2005 Web Application Project.

    Hope this helps,


  • Hi Elton,

    We are working on releasing localized versions of the patch now. I don't have a final ETA on the languages yet -- but it is definitely in the works.



  • Hi Lynn,

    Can you send me an email (scottgu@microsoft.com) with more details on your scenario? I'm not sure I understand it 100%.



  • Please, make autoeventwireup=&quot;false&quot; the default setting and have it auto-generate a new event in the xxx.aspx.designer.cs like VS2003 style. It blows to do this by hand as it is now.

    override protected void OnInit(EventArgs e)





    private void InitializeComponent()


    this.Load += new System.EventHandler(this.Page_Load);

    this.Button1.Click += new System.EventHandler(this.Button1_Click);


  • Hi, after installing RC1 I got a rather big problem with vs2005. I cannot drop any usercontrols (self programmed or bought) onto the designer. VS only tells me: &quot;control cannot be created because Visual studio cannot find the control's type in the control assembly&quot; what is rather sensless. The controls itself are functional when running the project...

    UserControl already present in the Page are not rendered correctly in the Designer, there the error is unkown server tag (although the server tags are registered correctly).

    Anyone having an idea?



    Ps: Nevertheless, great project could not live without it...

  • Scott,

    I just wanted to thank you and the team for all of the hard work you guys have put into this. I can't wait to start using it and keep up the good work.

  • Hi Scott,

    I am very happy to read about this release. I think it missing and I am sure it will be a very popular patch for the VS2005. Keep on the good work!

    Now business...

    I went through the tutorials in the dedicated website (one by one like a good kid) and eventually tried to migrate a very simple website I recently developed using WSM. I also used Atlas in it.

    I had some compilation errors after the whole procedure, which I managed to overcome. One important thing I had to deal with was the fact the the &quot;Convert to web application&quot; did not handle was Atlas controls. All pages using these controls were not parsed and I had to generate the &quot;.designer.cs&quot; files myself for them. Other then that it was pretty ok.

    There are two issues I want to discuss regaring Profile:

    1. In the tutorial it is mentioned that if the WSM application uses Profile, than I should create the ProfileCommon class myself (auto-generated in WSM). I am not sure whether the provided sample in the tutorial is correct. As I understand the ProfileCommon should extend ProfileBase. The sample code does not extend it.

    2. After making the whole Profile thing compile (extending ProfileBase and adding the Profile declaration in wach code-behind file that uses the Profile) I managed to run the site. But when I reached a page which uses Profile I got an error:

    The type 'college_Details' already contains a definition for 'Profile'.

    Source Error:

    Line 14: public partial class college_Details : System.Web.UI.Page {

    Line 15:

    Line 16: ProfileCommon Profile = new ProfileCommon();

    WOW... this was long...

    I would be happy to read your reply.



  • Hi Scott - any plans for having the facility to remove items on a remote host (rather than just the options to delete and recopy, or add new files)? Or does it detect local deletions already and process these on the remote site?

    Where I could see this useful is if a file is deleted in App_Code. If this happens, only by deleting the whole project on the remote site and republishing can it be removed. If it isn't removed this way, you may get errors on the remote host.


  • How do I migrate an existing VS 2005 website to a Web Application Project now? I see you mentioned a tutorial, but I don't see one and am not sure how to start.

  • Hi Scott,

    does the code generated by VS 2005 when using the Web Application Project compile under .Net 1.1 Framework?

    We are starting a new application but need to contain ourselves to 1.1 compatible code and we looking to use VS 2005 and MSBee.



  • This release makes me encounter a new error message underlining the whole &lt;%@ Page%&gt; declaration :

    &quot;Error 21 C:\Data\Projet.NET2\Company\WebSite\mySolution\Net\SubProject\myPage.aspx: ASP.NET runtime error: There is no build provider registered for the extension ''. You can register one in the &lt;compilation&gt;&lt;buildProviders&gt; section in machine.config or web.config. Make sure is has a BuildProviderAppliesToAttribute attribute which includes the value 'Web' or 'All'.&quot;

    Any ideas ?

    For info, my solution holds several aspx projects but only one is the main one with web.config inside and the others are in excluded subfolders.

  • Hello. I'm not clear what you mean by &quot;Support for building multi-project applications and sub-web projects&quot;. Are &quot;sub-web projects&quot; the same as &quot;User Control Libraries&quot; (as described in Tutorial 6). Or, is this something different? Thanks!

  • Scott,

    I am confused. What is the difference between this and the Web Deployment Project?



  • Scott,

    I'm really excited about being able to move to web app projects. However, when I see the list of features you've added and what situations they resolve, I start to get nervous about whether there are things that I'll be implicitly losing which I currently use via web site projects.

    For example, you listed &quot;SQL DataSource Control Support&quot; as a newly-added feature in the RC. If that wasn't supported in previous web app project releases, how did you work with SQL Data Source controls in those kinds of projects? Did designer support for setting data source properties and corresponding data-bound controls (e.g. GridView) not work in those releases? Since you didn't mention Object Data Source, is that not supported in the RC?

    I've spent time over the last couple of weeks writing an admin app for one of our systems. I'm using many of the techniques that you covered in your recent Atlas tutorial video (object data source, gridview, detailsview, etc.) so that I get a better feel for some of the areas of VS2005 and ASP.NET 2.0 that I haven't yet worked with. Will those techniques not work with web app projects? Could you not have done your tutorial as a web app project?

    I hope these questions make sense. Thanks for your efforts!


  • Hi Ekkehard,

    I'm not seeing this issue when trying it out. Can you send me an email (scottgu@microsoft.com) with more details and we can loop some poeple in to investigate?



  • Hi David,

    Can you send me a simple sample with your profile code (scottgu@microsoft.com)? I can then take a look and figure out what the issue is.



  • Hi Glyn,

    You can use the &quot;Copy Web&quot; utility within VS 2005 to open up and delete or move individual files on a remote site. The publish web dialog then has the ability to nuke and re-do everything, or to just to incremental add/update changes.

    Note that with VS 2005 Web Application Projects you don't actually publish the app_code directory -- since with this model the classes are all compiled into a project assembly and that is in turn published. So for app_code you don't need to worry (since there isn't one).

    Hope this helps,


  • Hi Tristan,

    When you debug you can set multiple breakpoints, and so probably the easiest way to-do what you are after is to just hit &quot;f5&quot; to continue after the first breakpoint to jump to the next one. That way you don't need to step line by line through each operation.

    Hope this helps,


  • Hi Chris,

    We are looking at possibly adding the strongly-typed Profile generation into the final release of WAP. For the release candidate, though, you need to manually create the Profile object.

    Note that the &lt;asp:ProfileParameter&gt; works already -- so that is unchanged by WAP.

    Hope this helps,


  • Thank you for this! The first thing I attempted when I received VS 2005 was to convert a large 1.1 project to 2.0. I have to admit that it was a letdown. But, with this release, I am throughly impressed with how you have your finger on the pulse of ASP.NET development. With this and your exciting presentations in Orlando, I can't wait to fully transition to 2.0. (Thanks for building your demos from scratch in a live situation!)

  • Hi Roger,

    The applications that are built with WAP use the standard ASP.NET and .NET Framework binaries -- so there aren't any issues with putting apps built with it into production. There also shouldn't be any issues upgrading to the final release of WAP with it (since the project file and code generation format will stay the same).

    XML Documentation is also fully possibly with Web Application Projects.

    Hope this helps,


  • I installed both updates and they went just fine. After a reboot, I still don't see the updated project properties screen or publish screen as you have in your blog. Any idea what I can check? I've been uninstalling/reinstalling all afternoon trying to get these to work!


  • Hi Andy,

    In theory you should be able to use MSBee for targetting 1.1 with VS 2005 Web Application Projects -- although I haven't tried it myself.

    One thing to watch out for is that you don't want to use partial classes in the project, since that isn't supported by 1.1 compilers. But if you avoid this and are careful elsewhere it should in theory work.

    Hope this helps,


  • Hi FredT,

    Can you send me an email (scottgu@microsoft.com) with more details on this? I can then help debug it and figure out what is going on.



  • Hi Kevin,

    I am planning on writing up a blog post on the sub-project/multi-project idea. It is different from user-control libraries, and actually allows you to have multiple projects working within the same application.



  • Hey Scott,

    Thanks for the response. I did see that tutorial but it sounded like the latest release had some more &quot;integrated&quot; functionality that would eliminate some of the manual stuff. Maybe I misunderstood.


  • Hi Donnie (aka Soccerdad &lt;g&gt;),

    You can actually use all features of ASP.NET with Web Applications project. We had a bug with the previous WAP preview where the SQLDataSource control was sometimes flaky at design-time -- but that was fixed with this most recent drop. ObjectDataSource is also fully supported.

    Hope this helps,


  • Hi Darrell,

    Are you creating the new project by choose File-&gt;New Project (and not doing File-&gt;New WebSite)? My guess is that you are creating a web-site project and not a web application project.



  • Hi Roger,

    A .settings file is created for WAP projects, but the actual connection string is persisted in the web.config file. That way you can just change this (for example: using the ASP.NET admin tool) at runtime if you want.

    Hope this helps,


  • Hi Bob,

    With this release candidate the web-site to web-application migration is much more automated. There are still a few manual steps to take, but the work to convert pages, user controls and master pages to the new project format does happen automatically.

    Hope this helps,


  • Hi Scott,

    When you say &quot;Support to Drag/Drop User Controls, StyleSheets, Images from Solution Explorer to designer&quot;, do you mean supporting drag/drop into the Markup view?


  • Hi Rory,

    You can drag/drop stylesheets and images into source view now (it will auto-generate the appropriate html text).

    You can also drag/drop these in WYSWIYG mode, as well as drag/drop user controls into the desinger. User controls now show up in WYWISYG (unlike the grey box in VS 2003).

    Hope this helps,


  • Scott, are release notes available for the RC1 build (which seems to be 60406)?



  • Great Stuff! Looking at the decision matrix for Web Project vs. Web Site Projects (what's in a name) there is almost no reason to use the &quot;new&quot; Web Site Project model.

    Did I overlook something or is there no support (yet) for Asp.Net 2.0 theme's in this RC?

  • Hi

    I recently converted a project to a Web Application Project and the

    Application_Start event no longer fires in my global.asax.cs file on our

    live Windows 2003 Server. It all works fine when running under XP on my

    local dev machine though.

    I have tried adding a new global.asax using the Add-&gt;New menu option, and

    then copying the code over but this hasn't fixed the problem.

    Has anyone encountered this at all?



  • Backing up files. Just wanted to know with the web publish feature if there was another option to create backups of files? It says I can delete them before publish or just overwrite them, wanted to know if there was a feature that would copy any file to be overwritten.

  • Hi Ward,

    ASP.NET 2.0 Themes are supported with this RC build.

    There are still a number of benefits that the Web Site Model has over the Web Project Model. One of the big ones is that it allows other tools (Dreamweaver, FrontPage, etc) to work better together with developers on web projects. It also has a nice make change, hit save, hit refresh model for development which can be super handy.

    Hope this helps,


  • Hi Ryan,

    Unfortunately there isn't any automatic way to backup files prior to publishing. What you could do, though, is first publish to another directory to backup an image of the app, and then publish to the actual deploy location.

    Hope this helps,


  • Hi Ben,

    Can you send me email (scottgu@microsoft.com) with more details about this? I can then help you debug it and get it fixed.



  • Hi Ben,

    When will be released the RTM?


  • Where does the WAP keep the solution (sln) file? I find the way Web site projects keep sln files in separate directories inconvenient and moving them is a pain.

    I like to keep all files together and am smart enough to not deploy the sln file when making the final web site.

  • Hi Rick,

    Our plan is to get feedback from customers the rest of this month, and then deliver the final RTM build at the end of this month or fist week of May.



  • Hi Ned,

    You can store the .sln file either in the same directory as the project, or in a parent directory. I think there is a checkbox in VS 2005 when you create new projects that lets you control this (&quot;Create New Directory for Solution&quot;).

    Hope this helps,


  • I was happily using the Beta 2 release of this. When the RC1 release became available, I uninstalled to B2 version and installed RC1. Since that, the IDE closes upon trying to load any project. Any idea what I did wrong?

  • Hi Scott,

    I solved my problem - after a little research I learned that beta products don't always uninstall as one would expect. I ran the &quot;vs_uninst_betas.exe&quot; program and did a repair of VS 2005. Not sure the repair was necessary but at any rate everything loads up fine now.

    Thanks by the way for your speedy response. It is quite reassuring to know that there are folks who can have an impact on the product that really care about what users are experiencing. I wish you would have been in a position on the VS team to require that WAP be included in VS 2005 from the get go!

    I see a whole lot of upside to the new web site model if you are just now switching over from classic ASP, but if you build and sell intranet web apps this model makes for a whole lot of new work just to get it to do what WAP does for free. I cannot imagine what life would have been like a year from now if our customers could simply modify source code on their web servers!

    Thanks again,


  • Excellent. I tried migrating a 2003 project a few months back and never got it migrated. Kept getting this weird error that I couldn't find any info on, needless to say i gave up. Tried migrating the same project today with this new support installed and it worked perfectly. Rock and rolls!

  • Is it possible to convert a VS 2005 Web Application Project to a VS 2005 Website?



  • Could you post the url to the documentation for converting a VS2005 Web Site projects to a Web Application project?

  • Hi Scott,

    Is there any update on when the final RTM will be available?

  • Hi Matt,

    Our plan is for the RTM release to ship the first week of May (so next week). Send me email (scottgu@microsoft.com) if you are interested in trying out the near-final build. We'd love to get some more eyes trying it out to find any last minute issues.



  • I'm having this exact problem. Managed to reproduce on an XP test machine that does not have Visual Studio, but can't find the fix. This is so far the only reference to anyone else having the problem that I can find.

  • Hi Ahurbanipal,

    Can you send me email (scottgu@microsoft.com) with more details? We can then try and figure out what is going on.



  • This support for the VS2003 projects is great and saves me a ton of rework. However, moving forward with my team's current design, we will still need to be able to create a project within an existing folder. When I try to create a new project in my web, it creates the project in a new folder -- I don't want that. I still want the .dll to go in the root bin folder, etc., not a new subfolder.

  • Hi JMK,

    You can change the output path of the assembly in the project's properties dialog to go in the parent root path. Just have the \bin directory location be: &quot;..\bin&quot;

    Hope this helps,


  • Bravo!

    I really like switching between design and code with F7 and also not locking the design mode while debugging.

    Keep up the good work.

  • Hi Steve,

    I haven't actually used the Report Server Project support myself (that is built by a different team from mine). So unfortunately I can't comment too much on it.



  • I am trying to incorporate Atlas to a Web Application Project manually. &nbsp;Will there be a wizard support next time?

  • Hi Samboy,

    Yep -- we will have a template wizard included in an Atlas refresh in the future that has built-in VS 2005 Web Application Project support. Until then, you can manually add the assembly reference and update the web.config files.

    Hope this helps,


  • Is Web Application project support master pages

    It ask for master.cs file even after build and deployed.

  • Hi Rajesh,

    Web Application Projects fully support master pages. My guess is that the reason it is asking for that file is because you've moved a master page from a web-site project to a web-application project and haven't fully converted it. This article describes how to-do this: http://webproject.scottgu.com/CSharp/Migration2/Migration2.aspx

    Hope this helps,


  • I have the same problem as Ben did regarding the global.asax. It seems as if the global.asax is never loaded. But it works fine on my XP local machine. But when deployed to 2003 servers it doesn't work. I'm not sure what to do.

  • Hi Ella,

    Can you send me email (scottgu@microsoft.com) describing your project and problem? I can then loop you in with someone who can help investigate and get this fixed for you.



  • Did you finally fix the problem about no firing the application_Start in global.asax
    after converting a project to a Web Application Project on a Windows 2003 Server. It all works fine when running under XP on my
    local dev machine though.

  • The download link doesn't work anymore

  • Hi Mai,

    You shouldn't have a problem with this. Can you double check that your directory on the IIS6 box is configured as an application.



  • Greetings,

    I just converted a project to WAP and I am having the Global.asax issue. On my test/dev machine, using VS2005 with XP - everything works great inside of my Global.asax - when publish and send up the wire to my Windows 2k3 box - none of my Global.asax events fire (Application_Start, Session_Start, Application_BeginRequest to name a few).

    I have tried to play around with the access modifiers - marking them protected from private, then public from protected with no luck.

    I found an article stating to name them with the "On" (i.e. Application_Start rename to Application_OnStart) that should do the trick - but no luck - works on my dev machine, does not work on my production machine.

    This is a disappointing development as everything was working so great until this point. Switching back to the old project format since this issue breaks my web app 100%...

  • Trying to create a new solution file in VS: File | New | Product | Other Project Types | Visual Studio Solution | Blank Solution

    Why is the checkbox for "Create Directory for Solution" always greyed out? It's checked and I don't want it checked. I am simply going to add a new .sln to a root directory of mine then start adding back in some existing web projects and directories to it later and it keeps creating a folder for me due to this option that's not accessible for me to uncheck.

  • Hi Adam,

    Sorry I missed your comment for some reason. Are you still having this issue? If so, can you please email me and I can help?



  • Hi Anonymous,

    If you want to send me email about this question, I can loop someone in on the project team who might be able to best answer this.



  • Can u please tell, if
    i am adding a strongly named assembly reference to my Website Project In VS 2005 they are not shown in bin folder of my project ?

  • Hi Neek,

    If you reference an assembly from the GAC, then it won't be copied into your \bin directory.

    Hope this helps,


  • Hi Scott,

    Was there ever a solution to the global.asax.cs code not running on a production Server 2003 environment? I have global.asax in the root of my application and global.asax.cs in the app_code folder, locally this works fine though when deployed to production it fails to run.

    Was there a common problem with the other peoples issues above?

    Many Thanks

  • Hi Kieran,

    Usually that error can happen because of one of two things:

    1) The directory pointing to the application root is not marked as an "application" within IIS. Go into the IIS Admin tool and make sure it is configured as an app.

    2) Make sure that the Global.asax file was deployed on the remote server. It could be that the file is not being copied - in which case the Global.asax events won't fire.

    Can you check these two steps and see if it fixes the problem? If not, can you send me email and I can help further.



  • Does anybody have a workaround for the Global.asax bug causing event code not to execute at all in some Windows Server 2003 configurations? This bug is causing me major grief on a production site.

  • Hi Joe,

    Can you send me an email with more details about the issue you are seeing? Also - can you check:

    1) The directory pointing to the application root is not marked as an "application" within IIS. Go into the IIS Admin tool and make sure it is configured as an app.

    2) Make sure that the Global.asax file was deployed on the remote server. It could be that the file is not being copied - in which case the Global.asax events won't fire.



Comments have been disabled for this content.