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

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

Martin Naughton — Sun, 07 Aug 2005 13:15:59 GMT

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

Thanks,
Martin

Visual Studio Beta 2 - Call out to help test Upgrade Wizard features for ASP.NET v1.x to ASP.NET v2.0 solutions

Eric Hammersley — Sun, 07 Aug 2005 21:33:59 GMT

The ASP.NET team needs your help!

Mon, 08 Aug 2005 03:00:41 GMT

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

Help us test the VS 2005 Upgrade Wizard!

Clare Dillon's Blog — Mon, 08 Aug 2005 12:46:59 GMT

Help us test the updated Upgrade Wizard features in VS 2005!
Visual Studio 2005 will automatically convert...

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

Marius CONSTANTIN — Mon, 08 Aug 2005 14:01:53 GMT

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

Wanna help ASP.NET Team with Upgrade Wizard in VS2005? Then please do.

Joteke's Blog — Mon, 08 Aug 2005 21:54:44 GMT

Wanna help ASP.NET Team with Upgrade Wizard in VS2005?

Joteke's Blog — Mon, 08 Aug 2005 21:55:17 GMT

Помоги команде ASP.NET протестировать 1.1 -> 2.0 Upgrade Wizard

Gaidar's Blog — Wed, 10 Aug 2005 12:00:14 GMT

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

Un nouveau wizard de migration (ASP.NET v1.x vers ASP.NET v2) pour VS 2005 beta 2

Fox Blogs — Wed, 17 Aug 2005 08:57:27 GMT

need help converting

Zeeshan — Sun, 21 Aug 2005 21:57:39 GMT

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?

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

mbund — Mon, 22 Aug 2005 09:33:45 GMT

Zeeshan,

You should send your comments to webwish@microsoft.com -- 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.

-Mike-

ASP.NET Team looking for upgrade wizard testers

Raimond Brookman — Fri, 26 Aug 2005 01:03:28 GMT

A new wizard that supports more upgrade scenarios

Visual Studio Beta 2 - Call out to help test Upgrade Wizard features for ASP.NET v1.x to ASP.NET v2.0 solutions

Eric Hammersley — Fri, 09 Sep 2005 23:36:45 GMT

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

Brian Buff — Mon, 26 Sep 2005 14:56:57 GMT

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

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

bgold — Thu, 29 Sep 2005 06:52:12 GMT

Brian Buff -- Make sure you send the log files and information to webwish@microsoft.com -- Michael Bundschuh will get back to you with more information.

Thanks!

-Brian

CodingMoments.com » Blog Archive » Visual Studio Beta 2 - Call out to help test Upgrade Wizard features for ASP.NET v1.x to ASP.NET v2.0 solutions

Sun, 09 Jul 2006 07:37:42 GMT

PingBack from http://www.codingmoments.com/2005/08/07/visual-studio-beta-2-call-out-to-help-test-upgrade-wizard-features-for-aspnet-v1x-to-aspnet-v20-solutions/