SourceGear Support

The thinking is, that you receive the unexpected error because you tried to bind to the wrong location.

Are you saying you get this error, even if you do everything correctly?

In your Error2.jpg, you will notice that you have selected $/AniteEDRM/Development but also, above that, you have the Project set to Development. So, based on what you have selected, the path it will try to bind to is $/AniteEDRM/Development/Development You need to select $/AniteEDRM . Then the proj...

Well it's good to hear that the first issue is working!

I'll have to do a bit of research to find out what, if anything, you can do to get the checkin comments for the scenario you described.

The Vault Classic Client was coded to the 1.1 MSSCCI spec, and therefore Visual Studio will continue to create the temporary files to detect source control capabilities.

If this causes undue pain in your build processes, we recommend using the Visual Studio Enhanced Client.

I'm noticing reports of similar occurrences, with slight variations. http://community.macrovision.com/showthread.php?t=178452 I don't recall ever having seen this problem with SOS before. It's my opinion that one of the Microsoft Tools is the culprit. Is it possible for you to try and bind with VSS?...

I'm sorry. I misread your first post. For some reason, I saw VSS 2005 when you actually wrote VS 2005.

Maybe something in this msdn forum thread can be of assistance.

Have you applied the VSS 2005 patch from Microsoft?

http://support.microsoft.com/kb/943847

Brian, we'll log a bug and investigate fixing this in the next release.

Can you please email me (via the email button below this post) and we'll try to help you further, offline.

Haha. Well that wasn't as helpful as I'd hoped.

Can you please try disabling the SOS option to "Display Pin Status"? And then do a normal Open From Source Control.

I'm hesitant to have you go through all of this again, but it would be really helpful, if you could capture the text in the Output window and attach it please.

I'm so sorry, Brian. I wasn't clear. 1. Delete the entire solution off of local hard drive 2. Open up the SOS GUI and get latest version of the Entire Solution 3. Open Visual Studio and choose File->Open Project/Solution... Navigate to the solution that you just downloaded and select it. 4. Go to Fi...

That is actually very useful! If I'm understanding everything correctly, you should now have everything working in Visual Studio... albeit nothing is under Source Control. What we can do now, is go to File->Source Control->Change Source Control... and Rebind every project to its location in the repo...

Steps 1 & 2 are correct.

For step 3, don't do an Open From Source Control. Instead, simply open Visual Studio and choose File->Open Project/Solution...

Navigate to the solution that you just downloaded and select it.

Ok. If you use the SOS Gui client to download the Setup project manually, will Visual Studio then work with it?

Have you applied the VSS 2005 patch from Microsoft?

http://support.microsoft.com/kb/943847

I think applying this patch will solve your issue. Let us know if it doesn't.