This post originated from an RSS feed registered with .NET Buzz
by Brendan Tompkins.
Original Post: Our Upgrade from ASP.NET 1.1 to ASP.NET 2.0
Feed Title: Brendan Tompkins
Feed URL: /error.htm?aspxerrorpath=/blogs/brendan.tompkins/Rss.aspx
Feed Description: Blog First. Ask Questions Later.
Friday morning, I began the process of upgrading our public web site solution from ASP.NET 1.1 to 2.0. Our public web solution contains over 20 projects and a fair amount of code. After one day of work, itâs Monday morning and Iâm basically doneâ¦
I did run into one snag, and it had to do with accessing our WSE 2.0 Web Services from .NET 2.0. After the conversion, all of my WSE 2.0 code was deleted. I did some research and mistakenly cam to the conclusion that I had to run WSE 3.0 with ASP.NET 2.0, which would mean converting all my services to 3.0 as well. I wasnât looking forward to the amount of work this would entail, not to mention the logistical problem of updating many production apps that had this WSE 2.0 service dependencies. Thankfully, Friday night I spoke with a friend who told me that WSE 2.0 works fine with .NET 2.0 and all I needed was SP3.
What actually had happened was that the conversion process deleted all of my WSE stubs (dunno why) from my auto generated web service proxies. If youâve used WSE, you know that you get a [WebMethodName]Wse version of each web method, and thatâs the proxy that you use when you need WSE support. Well, the converter deleted these proxies, and I couldnât get them back without reverting the code. Finally what I did to fix this was to let the conversion run, and then get the previous version of the proxies from source control. This allowed me to build and after some testing the WSE 2.0 stuff seems to be working fine. So, this turned out to be more of a conversion issue than an actual technical one, thank goodness.
The VS team did a great job with the converter, and provided the following links that you should read before getting started:
If the application you are converting is of reasonable size and has several Web projects and additional projects, such as class libraries, in a single Visual Studio solution, it is possible to encounter issues during migration. Be prepared to spend the better part of a day completing the entire process.
Common ASP.NET 2.0 Conversion Issues and Solutions
So, Iâm done with the conversion, and by that I mean I get a clean build and can launch and run the site. I am by no means done, and ready to go into production. Iâd guess that Iâm about two weeks away from that. Now comes the hard part of finding out what actually broke, and the tedious task of testing everything, and then figuring out what all this App_Code/Migrated stuff is all about.
Previous Topic
