Error Binding VS2005 Solution

ICOM · Post by **ICOM** » Tue Jul 03, 2007 4:50 pm

I'm trying to follow the instructions at:
http://support.sourcegear.com/viewtopic.php?t=7937
But during the "Right-click on the solution and select "Bind" from the context menu." step, I get the following error:

Unable to cast object of type 'SourceGearLLC.VaultVsipClient.SolutionAndProjectNode' to type 'SourceGearLLC.VaultVsipClient.SolutionNode'.

I'm using Vault 4.0.1.15780 Client and Server with VS 2005 8.0.50727.762 and VS.PHP 2.3.2.3822

Any suggestions?

ICOM · Post by **ICOM** » Tue Jul 03, 2007 5:02 pm

I seem to have been able to work around it by first doing an "unload project", then the bind, then a "reload project".

ICOM · Post by **ICOM** » Wed Jul 04, 2007 11:13 am

Well, that worked around it for that particular task, but things like "Add to Vault" (for a new file) generate the same error afterwards.

Post by **jeremy_sg** » Thu Jul 05, 2007 7:52 am

There's probably an interaction with the vs.php project. Can you turn on Vault client logging and reproduce this? It would help us track down the problem. When you have a log file, email it to me using the button below this post.

ian_sg · Post by **ian_sg** » Thu Jul 05, 2007 12:40 pm

Thanks for the log. I see you're doing PHP work in Visual Studio. Are you using VS.Php 2.3?

ICOM · Post by **ICOM** » Thu Jul 05, 2007 2:52 pm

Yes, 2.3.2.3822 as stated in my first post.
The vs2003 plugin seemed to work without problems, so I just assumed 2005 would be the same. Perhaps I should have asked first.

Manually looking at my .phpproj file, it appears that using 2003, it had the following in the "General" section:

Code: Select all

"SccProjectName" = "$/Code"
"SccLocalPath" = "."
"SccAuxPath" = ""
"SccProvider" = "MSSCCI:SourceGear Vault VS2003 Compatible Client"
"ProjectIdGuid" = "{ACEDC810-AC42-4E51-81DC-B39D3F8A7D22}"
"ProjectVersion" = "2.3.2.3822"

While since attempting to switch to 2005, it no longer contains any of the Scc lines.

I'm not sure if the 2005 plugin is intended to have that information as well, or if that information has been moved elsewhere.

Similarly, the sln file was updated from:

Code: Select all

	GlobalSection(SourceCodeControl) = preSolution
		SccNumberOfProjects = 2
		SccProjectUniqueName0 = FiLMS\u0020v3.phpproj
		SccLocalPath0 = .
		CanCheckoutShared = false
		SccLocalPath1 = .
		CanCheckoutShared = false

to

Code: Select all

	GlobalSection(VaultVsipSolution-v2) = preSolution
		VaultHost = http://icomnt05/VaultService
		VaultRepositoryID = 6
		VaultRepositoryGUID = 5b34414d-72a9-4ec9-b5e5-f3c369fb97da
		ProjectCount = 0

ian_sg · Post by **ian_sg** » Fri Jul 06, 2007 8:45 am

Yes, 2.3.2.3822 as stated in my first post.

Sorry, I missed that. We'll look into this, it looks like some behavior unique to VS.Php projects that we're not handling. In the mean time, your best workaround is to run with the 2003-compatible client.

ICOM · Post by **ICOM** » Fri Jul 06, 2007 1:04 pm

Thank you. I will continue to do so.

vsphp · Post by **vsphp** » Sat Jul 07, 2007 5:08 am

I'm one of the developers of VS.Php. Let me know what's wrong and we can work out a fix together.

ian_sg · Post by **ian_sg** » Sat Jul 07, 2007 7:33 am

Thanks, we'll do that. At this point I consider it likely that we'll be able to make it work without changes on your end, but I'll certainly let you know if we find otherwise.

ICOM · Post by **ICOM** » Tue Jul 24, 2007 11:53 am

Any updates?

ian_sg · Post by **ian_sg** » Tue Jul 24, 2007 12:55 pm

Not yet. It's on the list, but I have nothing interesting to report at this time.

ICOM · Post by **ICOM** » Tue Jul 24, 2007 12:56 pm

Thanks. Keep me informed.

ICOM · Post by **ICOM** » Tue Aug 28, 2007 4:56 pm

Should I keep checking in periodically like this, or will you post back here as soon as this is fixed?

ian_sg · Post by **ian_sg** » Tue Aug 28, 2007 7:02 pm

I'll post back here.