I want to first say that I am not a very experienced programmer, and my job right now is requiring me to migrate quite a few ASP.NET 1.1 projects to ASP.NET 2.0. This is what I am doing:
Open VS2003, go to File -> Source Control -> Open From Source Control
The source control is Visual SourceSafe 6.0.
I make sure the web application is working correctly, nobody else has any files locked, compile it, and exit.
I then open VS2005, go to File -> Open File -> and open the project that I'm working on.
The conversion wizard opens up and I follow the instructions, back up the app, and finish. After the wizard works for a moment, I get a very ambiguous error log saying only that there were errors. No error report or anything.
Am I missing steps? Is the fact that the application is in VSS an issue? How do I circumvent this problem so that this can be migrated.
Also, I have the VS2005 SP1 2.0.50727 installed.
Please, any help would be much appreciated.
Web Application Projectsvisual studio 2005ASP.NETSteps to migrate?asp.NET 2.0web site project
I've never had much luck with the wizard. I've converted a lot of applications and usually do it manually. It's been a little while, but my steps typically go like this:
Create a new blank website project in 2.0. Leave the web.config and add a new global.asax
Bring in the 1.1 files via Add Existing item, for aspx pages if you just bring in the aspx it will automatically grab its dependent files (codebehind, etc). I do not bring in the web.config or global.asax
I step through a find and replace and rename all my public class declarations in the codebehinds for the aspx pages to partial class
I step through again renaming all the page declarations to use CodeFile= versus CodeBehind
Also, in the page declarations, if the project name is prepended to the Inherits attribute, I remove it so Inherits matches the class name of the codebehind file
I bring over only the necessary contents of the web.config into the new web.config as this file is structured differently between 1.1 and 2.0
I bring over the global.asax contents. 2.0 handles the global.asax file differently and if you use a codebehind it will put it in the App_Code folder. Leave page declaration as CodeBehind (not CodeFile) and you may need to tinker with it a bit
Any straight code modules (not bound to an aspx page) should also go in your app_code folder
Then I go through the business of trying to get it to compile and resolving any errors, which can be numerous if the code quality of the 1.1 app has some problems
That's a general summary, not meant to be a step by step set of instructions that will work without issue, just recalling generally what I go through.
If you plan to stick with the wizard, I don't know why your report wouldn't be visible; it's usually a hyperlink and is also stuck in a file in the new project directory I think.
And lastly, I convert with a copy completely out of source control and writable. After the project is in it's new home and compiling I hook it back up to source control.
Bruce
Please remember to click "Mark as Answer" on the posts that helped solve your issue.
One other important step I forgot to mention that would go in between 3 and 4, I find all the sections in the codebehind files under the "Web Form Designer Generated Code" region and remove, as this is now handled by the partial class paradigm in 2.0. If
there are items in the Init event that are not related to items in the designer, they should be moved to their respective page event handlers.
Bruce
Please remember to click "Mark as Answer" on the posts that helped solve your issue.
Thanks for the help. I've figured out a solution to my problem. What I wasn't doing, but only realized after extensive research on the web, was not checking out my project in VS.NET 2003. VSS still had source control over the document, and therefore
VS2005 would not do the migration. However, I do want to say that the tips you provided are going in a document so that I can use them in the future.
Chris
Marked as answer by cdbiggs on Aug 05, 2008 02:19 PM
cdbiggs
0 Points
15 Posts
Seriously confused...
Aug 04, 2008 09:19 PM|LINK
I want to first say that I am not a very experienced programmer, and my job right now is requiring me to migrate quite a few ASP.NET 1.1 projects to ASP.NET 2.0. This is what I am doing:
Open VS2003, go to File -> Source Control -> Open From Source Control
The source control is Visual SourceSafe 6.0.
I make sure the web application is working correctly, nobody else has any files locked, compile it, and exit.
I then open VS2005, go to File -> Open File -> and open the project that I'm working on.
The conversion wizard opens up and I follow the instructions, back up the app, and finish. After the wizard works for a moment, I get a very ambiguous error log saying only that there were errors. No error report or anything.
Am I missing steps? Is the fact that the application is in VSS an issue? How do I circumvent this problem so that this can be migrated.
Also, I have the VS2005 SP1 2.0.50727 installed.
Please, any help would be much appreciated.
Web Application Projects visual studio 2005 ASP.NET Steps to migrate? asp.NET 2.0 web site project
BHendry
Participant
1644 Points
297 Posts
Re: Seriously confused...
Aug 04, 2008 10:21 PM|LINK
Hi cdbiggs,
I've never had much luck with the wizard. I've converted a lot of applications and usually do it manually. It's been a little while, but my steps typically go like this:
That's a general summary, not meant to be a step by step set of instructions that will work without issue, just recalling generally what I go through.
If you plan to stick with the wizard, I don't know why your report wouldn't be visible; it's usually a hyperlink and is also stuck in a file in the new project directory I think.
http://msdn.microsoft.com/en-us/library/aa479312.aspx
And lastly, I convert with a copy completely out of source control and writable. After the project is in it's new home and compiling I hook it back up to source control.
Please remember to click "Mark as Answer" on the posts that helped solve your issue.
BHendry
Participant
1644 Points
297 Posts
Re: Seriously confused...
Aug 05, 2008 02:00 PM|LINK
One other important step I forgot to mention that would go in between 3 and 4, I find all the sections in the codebehind files under the "Web Form Designer Generated Code" region and remove, as this is now handled by the partial class paradigm in 2.0. If there are items in the Init event that are not related to items in the designer, they should be moved to their respective page event handlers.
Please remember to click "Mark as Answer" on the posts that helped solve your issue.
cdbiggs
0 Points
15 Posts
Re: Seriously confused...
Aug 05, 2008 02:19 PM|LINK
Bruce,
Thanks for the help. I've figured out a solution to my problem. What I wasn't doing, but only realized after extensive research on the web, was not checking out my project in VS.NET 2003. VSS still had source control over the document, and therefore VS2005 would not do the migration. However, I do want to say that the tips you provided are going in a document so that I can use them in the future.
Chris