Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Aug 05, 2008 02:19 PM by cdbiggs
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
Steps to migrate?
web site project
Aug 04, 2008 10:21 PM|LINK
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.
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.
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.
Aug 05, 2008 02:19 PM|LINK
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.