The time eventually arrived at work when we had to upgrade an asp.net web application from asp.net 1.1 to asp.net 2.0 and embrace visual studio.net 2005.
We started by retrieving the latest version of the web application using visual studio.net 2003 which was under source control (visual source safe 6).
As a safety precaution all access to the visual source safe project containing the web application was revoked to stop any part of the migration wizard modifying the asp.net 1.1 version of the web application.
The latest version of the web application was copied to a different machine where the migration wizard was started by openning the solution using visual studio.net 2005. Unfortunately the wizard did not make much progress as it tried to communicate with visual source safe to remove the source control bindings which is part of the migration wizard. It failed to do this as we had revoked access. We manually edited the solution file to get round this problem.
The migration wizard ran for some time before presenting us with a report about the status of the migration. A number of errors existed in the report because certain pages / user controls had codebehind declarations to files which did not exist.
Looking through the migrated web application it had created a stub class file for every page which seems a but uneccessary, moved all the class files to the app_code folder, adding a namespace declaration to each existing class file, adding references to the web.config and a few other things.
Tuesday, January 9, 2007
Subscribe to:
Post Comments (Atom)
0 comments:
Post a Comment