SOS 4.2 and VS 2008

If you are having a problem using SourceOffSite, post a message here.

Moderator: SourceGear

Post Reply
plumriver
Posts: 2
Joined: Wed Feb 27, 2008 8:23 am

SOS 4.2 and VS 2008

Post by plumriver » Mon Mar 03, 2008 12:08 pm

Hello,

I'm having an issue with Sorce Off Site in Visual Studio 2008. When in VS 2008 I go to the File --> Source Control --> Open from Source Control...
then connect to the SOS and select the folder where the solution is and then it starts a converson wizard. Then during that process I'm getting this error:

Your source control plug-in caused an exception or reported a fatal error.
Source control integration will be disabled until Microsoft Visual Studio is restarted or you change your source control plug-in selection.

This happens on Windows Vista Business, 32-bit OS.
Source Off Site client v. 4.2 (no cryptography)
Visual Studio 2008.
The solution I'm trying to open is .NET Framework 2.0.

I would appreciate any help.

Thanks

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Post by Beth » Mon Mar 03, 2008 2:38 pm

Was the solution a VS 2005 or earlier solution before?

plumriver
Posts: 2
Joined: Wed Feb 27, 2008 8:23 am

SOS 4.2 and VS 2008

Post by plumriver » Mon Mar 03, 2008 2:47 pm

Yes, the solution was created with VS 2005. But since I want the solution to open in VS 2005 and VS 2008, I copied the original .sln file, renamed it and added to the SOS. When I open the solution from SOS I am openning the one I wish to upgrage to VS 2008 version.

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Post by Beth » Mon Mar 03, 2008 3:56 pm

Visual Studio might write different information to the project files as well in VS 2005 versus VS 2008. I haven't heard of a solution or project needing to be worked on in both.

Probably your best bet will be to branch your entire solution, perform a fresh Open From Source Control on that branch, unbind it, make sure the references all point to the correct location (not the original files, but to a copy of the files), then convert it, rebind it to source control, and then check in the changes. Basically, these would need to be treated as completely different projects and solutions.

Normally, for converting, I'd have a user perform the same actions as when converting from VS 2003 to VS 2005. That's a one way conversion though.

Post Reply