Help us test the updated Upgrade Wizard features in VS 2005!

We need your help testing the new and improved upgrade experience with Visual Studio 2005 and ASP.NET 2.0

Are you interested in upgrading your web application from ASP.NET 1.x to 2.0?
Well then you have come to the right place, because I have a brand new prototype of our latest and greatest upgrade wizard that we want to test to see how it converts your existing Web projects.

So go on ahead and grab Visual Studio 2005 BETA 2 (Visual Web Developer 2005 Express Edition works too! but nothing newer, none of the CTP’s, 50215.45 only)

This prototype includes fixes to:

1. Handle code-behind to code-behind assembly references
2. Allow stand-alone class files to access web forms and user controls
3. Handle extra classes, structs, etc., found in code-behind files

Download the new binaries here (

It contains two Beta 2-compatible libraries which you can replace in your Beta 2 installation of Visual Studio 2005/VWD Express.
Please follow the steps found in the README file in the zip file to install the updated upgrade wizard.
A white paper outlining common upgrade issues can be found here with even more information at the upgrade center on MSDN

Visual Studio 2005 will automatically convert your ASP.NET 1.x web application when it is opened in the IDE. Our goal is to minimize the amount of coding you need to do manually after running the migration wizard and we need your help!

To measure how successful the migration wizard performs, we ask you to send in a simple 3 question survey (see below), along with your conversion report and any reported error and warnings to

1. Did your web application BUILD after the migration wizard was done?
2. Did your web application run after the migration wizard was done?
3. If not, then how long did it take to fix the build and/or run-time issues?
    a. less than an hour
    b. 1-4 hours
    c. 4-8 hours
    d. more than 8 hours
    e. Unable to finish migration yet

Remember, please send your survey to and attach your conversion report (found in your web application folder) along with any errors and/or warnings shown in Visual Studio 2005 when you build or run your project.

Thank you for helping us, we are looking forward to your feedback.

Comments (16)

  1. Martin Naughton says:

    Hi Brian,

    Thanks for the update. I have one observation, regarding Web Service proxies in a Web Application.

    It would be helpful if you could advise the most pragmatic approach to converting Web Service proxies whose code has been modified from that generated by the WSDL.EXE utility.

    For the purpose of this discussion, let’s assume that the code modifications are unavoidable.

    If, for whatever reason, the Web Service proxy code has been edited after it has been generated, the migration process may result in broken code, since those changes will be lost with the removal of the generated code.

    I am considering the following approach, to test whether migration works as desired:

    1) Take a copy of the Reference.cs/.vb file – the file that contains all the generated Web Service Proxy code.

    2) Remove the Web Reference from the project.

    3) Add the Reference.cs/.vb file as a "standard" code file.

    4) Attempt migration

    Do you think this approach will work smoothly?

    Is there a better approach?

    Could the migration utility be enhanced, to offer the developer the opportunity to:

    a) Migrate in the default way (i.e. as done now)

    b) Migrate in such a way as not to remove the Reference.cs/.vb file



  2. You have a chance to make a difference…the ASP.NET team is looking for help testing the ASP.NET 1.x…

  3. Help us test the updated Upgrade Wizard features in VS 2005!

    Visual Studio 2005 will automatically convert…

  4. I haven’t tested yet the new Upgrade Wizard, but I have one comment: I would like to get an option not not convert my aspx and aspx.cs files to partial classes. When Visual Studio 2005 will appear we would like to stick for a period in targeting framework 1.x, and it is a major inconvenience to reconvert a 150-200 aspx files project back to regular classes, not partial

  5. Команда ASP.NET хочет протестировать новые возможности мастера миграции ASP.NET

  6. Zeeshan says:

    i dont think i would ever get my project to convert one error after another. i first tried the july ctp release came across so many errors that after spending 2 weeks gave up on it. then someone gave me the link to over here so i tried the coverter above with beta 2 dont know if it is newer then july ctp release. anyways the following error is among tons of other coversion erors

    Circular file references are not allowed

    how do i reslove this issue.

    i have a usercontrol that was dropped onto the page obviously it therefore had a reference to in the aspx file something like this

    the page is ~/common/menu.aspx

    <%@ Register TagPrefix="uc1" TagName="maintmenu" Src="../maintenance/maintmenu.ascx" %>

    but on the usercontrol i was accessing a page property therefore the converter actually put a reference to common/menu.aspx so i can access the page property something like this

    <%@ Reference Page="~/common/menu.aspx" %>

    so both are referencing each other i guess and that is what visual studio is complaining so what to do now?

  7. mbund says:


    You should send your comments to — we are collecting user feedback and tracking user problems there. Please make sure you send in the conversion report and any build errors you get.

    FYI, the new upgrade wizard mentioned in this blog contains features newer than the July CTP.


  8. A new wizard that supports more upgrade scenarios

  9. Brian Buff says:

    After running my site through the VS2005 RC Upgrade Wizard, I now have a ton of "Circular file references are not allowed" errors relating to my User Controls. Any idea on how to solve this at the circular reference isn’t obvious at all?

    Thanks in advance

  10. bgold says:

    Brian Buff — Make sure you send the log files and information to — Michael Bundschuh will get back to you with more information.