Just open the solution with Visual Studio 2012 and the conversion dialog will appear. Go through the steps and you'll be upgraded. You may have to modify some of the code after the conversion due to compatibility issues, but the rest of the process should
be fairly straight-forward. I recently upgraded from 2003 to 2010 and had no problems. I've upgrade from 2005 to 2012 and didn't have problems on a different project.
If you use Visual SourceSafe you are going to run into problems and will want to get rid of the vspscc, vsscc, and scc file extensions. Any other source control shouldn't cause any problems, but no guarantees. Preferrence for VS projects is Team Foundation
Server.
I recommend making a backup before attempting the conversion. Though Visual Studio will give you the opportunity to make a backup during the conversion process.
Getting this when Im trying to update the project...
Could not find the server 'http://localhost/WebPLR/Web_PLR.csproj' on the local machine. Creating a virtual directory is only supported on the local IIS server.
Can you get to the project settings within Visual Studio? From the sound of it, I assume the answer is "No." But if you can get the project settings open in VS, then go to the "Web" tab and under the "Servers" section make sure that "User Visual Studio Development
Server" is selected. It's likely these settings are currently configured to "Use Local IIS Web server."
You may be able to do this in VS2003 prior to attempting the conversion and I recommend doing it that way if possible.
If you can't get to the project settings in VS2003 or newer then you may have to edit the Web_PLR.csproj file in a text editor to remove some references to IIS before attempting the conversion. We may need you to post the content of your project file(s)
in order for us to help further.
I haven't played around with project files much, but here's what I would try.
Make a backup of the file first
Modify the "ORIGINAL_PROJECT_FILE_PATH" to point to the local path on your computer (i.e. C:\Users\MyUser\My Documents\Visual Studio 2012\Projects\Web_PLR.csproj). Attempt to launch into Visual Studio.
You can probably remove the "SOURCE_CONTROL_SETTINGS_PROVIDER" and "FILE_VERSION" options, but Visual Studio should allow you to unbind the project from source control during the conversion. I'm not sure how picky Visual Studio is with the other options.
A last resort is to create a new project in Visual Studio and just copy the resources over to the new project from the old one. It would be dissappointing if you had to go that route, though.
AlonQ
Member
21 Points
61 Posts
Upgrade VS2003 Solution to VS2012
Nov 21, 2012 06:36 PM|LINK
Is there a way to do this?
KJAK
Participant
1673 Points
478 Posts
Re: Upgrade VS2003 Solution to VS2012
Nov 21, 2012 07:01 PM|LINK
Just open the solution with Visual Studio 2012 and the conversion dialog will appear. Go through the steps and you'll be upgraded. You may have to modify some of the code after the conversion due to compatibility issues, but the rest of the process should be fairly straight-forward. I recently upgraded from 2003 to 2010 and had no problems. I've upgrade from 2005 to 2012 and didn't have problems on a different project.
KJAK
AlonQ
Member
21 Points
61 Posts
Re: Upgrade VS2003 Solution to VS2012
Nov 21, 2012 07:03 PM|LINK
Will there be a problem is the project is attached to Source Control... or should I just unbind it
KJAK
Participant
1673 Points
478 Posts
Re: Upgrade VS2003 Solution to VS2012
Nov 21, 2012 07:08 PM|LINK
If you use Visual SourceSafe you are going to run into problems and will want to get rid of the vspscc, vsscc, and scc file extensions. Any other source control shouldn't cause any problems, but no guarantees. Preferrence for VS projects is Team Foundation Server.
I recommend making a backup before attempting the conversion. Though Visual Studio will give you the opportunity to make a backup during the conversion process.
KJAK
AlonQ
Member
21 Points
61 Posts
Re: Upgrade VS2003 Solution to VS2012
Nov 21, 2012 07:15 PM|LINK
I use Team Foundation Server... hopefully it wont give me trouble then :D... will try now and comeback later if I need help with something :D
AlonQ
Member
21 Points
61 Posts
Re: Upgrade VS2003 Solution to VS2012
Nov 21, 2012 08:09 PM|LINK
Getting this when Im trying to update the project...
KJAK
Participant
1673 Points
478 Posts
Re: Upgrade VS2003 Solution to VS2012
Nov 26, 2012 01:49 PM|LINK
Can you get to the project settings within Visual Studio? From the sound of it, I assume the answer is "No." But if you can get the project settings open in VS, then go to the "Web" tab and under the "Servers" section make sure that "User Visual Studio Development Server" is selected. It's likely these settings are currently configured to "Use Local IIS Web server."
You may be able to do this in VS2003 prior to attempting the conversion and I recommend doing it that way if possible.
If you can't get to the project settings in VS2003 or newer then you may have to edit the Web_PLR.csproj file in a text editor to remove some references to IIS before attempting the conversion. We may need you to post the content of your project file(s) in order for us to help further.
KJAK
AlonQ
Member
21 Points
61 Posts
Re: Upgrade VS2003 Solution to VS2012
Nov 26, 2012 05:07 PM|LINK
""
{
"FILE_VERSION" = "9237"
"ENLISTMENT_CHOICE" = "COMPULSORY"
"PROJECT_FILE_RELATIVE_PATH" = ""
"NUMBER_OF_EXCLUDED_FILES" = "0"
"ORIGINAL_PROJECT_FILE_PATH" = "http://localhost/WebPLR/Web_PLR.csproj"
"NUMBER_OF_NESTED_PROJECTS" = "0"
"SOURCE_CONTROL_SETTINGS_PROVIDER" = "PROVIDER"
}
This is the content of Web_PLR.csproj
KJAK
Participant
1673 Points
478 Posts
Re: Upgrade VS2003 Solution to VS2012
Nov 27, 2012 02:05 PM|LINK
I haven't played around with project files much, but here's what I would try.
Make a backup of the file first
Modify the "ORIGINAL_PROJECT_FILE_PATH" to point to the local path on your computer (i.e. C:\Users\MyUser\My Documents\Visual Studio 2012\Projects\Web_PLR.csproj). Attempt to launch into Visual Studio.
You can probably remove the "SOURCE_CONTROL_SETTINGS_PROVIDER" and "FILE_VERSION" options, but Visual Studio should allow you to unbind the project from source control during the conversion. I'm not sure how picky Visual Studio is with the other options.
A last resort is to create a new project in Visual Studio and just copy the resources over to the new project from the old one. It would be dissappointing if you had to go that route, though.
Good luck
KJAK