Better way to move VS2003 solutions to new machine?

[DesertDude]

I am moving my VS2003 projects to a new machine. Here's what I did:

On the old machine:

1. I checked in the entire solution. It should be noted that my sln file is not in the same folder as my other files. The sln file is in MyDocuments\Visual Studio Projects, while the other project files are in a folder in wwwroot.

On the new machine:

2. I created a new project so that it registered the new directory with IIS.

3. In the Vault Client, I pointed the working directory of the checked in project to the directory created in step 3.

4. I checked out the project in the Vault Client.

5. I opened VS2003 and opened the project. I got this message:

The solution appears to be under source control, but it's binding information cannot be found. It is possible that the MSSCCPRJ.SCC file or another item that holds the source control settings for the solution, has been deleted. Because it is not possible to recover this missing information automatically, the projects whose bindings are missing will be treated as not under source control.

When I click OK on this message, the project shows up, seemingly OK.

6. I undid the checkout in the Vault Client and deleted the project folder in there.

7. I added the project to source control from within VS2003.

Everything seems fine, but because of step 6, I have lost the history for that solution in Vault. This is a new solution, so I'm not that concerned, but I have others I need to move to the new machine. There must be a better way to do this. Any ideas?

Thanks.

[lbauer]

Yes, there's a better way.

If you want to bring a solution/project to a new machine, do a fresh open from source control with Visual Studio. The command is under File->Source Control->Open From Source Control. This creates the proper bindings and the MSSCCI.prj file that is needed.

If you get the project with the GUI Client, none of these binding are created.

For more information about using Vault with VS.NET 2003 web projects, see this KB article:

http://support.sourcegear.com/viewtopic.php?t=35

[DesertDude]

thanks for the reply, Linda. Just a couple of follow-up questions:

Do I create the project on the new machine first as I did? If so, do I then do the "Open from Source Control" you mentioned, from within the already opened and created project? Will this not cause any conflicts since the project is already open, albeit an "empty," new one?

Also, after performing the steps I outlined, when I check out the project to the new machine, I get the expected checkmarks next to the items in VS2003; however, the are accompanied by little red exclamation marks. I can't see how to find out what it's complaining about...

Thanks, again!

[lbauer]

Do I create the project on the new machine first as I did? If so, do I then do the "Open from Source Control" you mentioned, from within the already opened and created project? Will this not cause any conflicts since the project is already open, albeit an "empty," new one?

In VS 2003, if a web project is properly added to source control (Meaning the solution file is in the parent folder of the project -- see the KB article mentioned in my earlier post), you should be able to Open from Source Control, select the folder with the solution, and the project will be automatically created on your machine in C:\Inetpub\wwwroot.