Source Gear and Visual Studio 2005

sdunn · Post by **sdunn** » Tue May 03, 2005 2:27 pm

I have a web project created in visual studio 2005 that I want to use with my Source Gear server. When I created the project it complained about files being in different locations, which is because the Solution File and other related source control files are located in my visual studio 2005 directory in my documents. That worked and I was able to check in files and check out files. Problem comes in when I want to have another developer on my team bind to the source control project. I copied the project directory to his machine (before it had source control bindings) and tried to manually bind to the project in Source Gear. It would not validate. Is there some easier way to do this?

I tried copying the files that were in my Visual Studio 2005 diretory in my documents to the project directory but that caused problems with people having control of checking out the solution file. It would lose bindings and such when getting latest files! HELP! Dont make me go back to Visual Source Safe! AHHHHHHHH !

dan · Post by **dan** » Tue May 03, 2005 3:51 pm

The second user should do an Open From Source Control from within Visual Studio to create the correct bindings. Hopefully after that, everything will work correctly.

Also, does VSS have the same issues? With VS 2005 betas, it might be the IDE rather than the scc providers.

sdunn · Post by **sdunn** » Tue May 03, 2005 8:56 pm

I dont know how VSS does things as I am trying not to use them from pains of the past. That is why I am using Source Gear. My question is this then. ASP.NET 2.0 projects are directory based but they do place four files in the DOCUMENTS\Visual Studio 2005\Projects\MyProject folder that are solution files and source control files. Should I move these to my root directory of my project? If I do and I add the project to Vault I do not get any errors that the project has files and that the Working Folder is C:\ but what I dont want is problems with the files after having to have someone check out the sln file to add things.

dan · Post by **dan** » Tue May 03, 2005 9:12 pm

Yes, the solution file should be at the root folder of all your projects, or you will have working folder problems. A web project can actually exist in a different location (since it becomes a virtual folder in IIS, and can be put under inetpub seperately from the other projects), but the safest thing is to keep them all under one common root.

Once you add them all to Vault (via Visual Studio), other users should use Open From Source Control to open the project. Don't copy files from one machine to another, as that will copy user and machine-specific info too. Once a user opens the solution from source control, it should work fine for them.

One other note is that VS 2005 is still in Beta, and doesn't always work correctly with Vault. We plan to have a Vault 3.1 out this month that will be compatible with VS 2005 Beta 2, but let us know if you run into problems.