The quick fix is: Delete the sln file and the vb project file in VSS (or
temporarily rename first if you're afraid this help could be a big mistake).
And the next time you open your solution add your new solution files.
The good fix is: Next time do "Get latest..." from the VSS to your working
directory first (overwriting anything you have there) then open the solution
file or the project file from that downloaded directory. :)
VSS and VS.NET get a little tricky in this regard... but once I figured out
their relationships and "assumed/observed" some of VSS processes they work
pretty well together.
Hope this helps.
Good luck,
/Js.
"Hector Garza" <ma********@hot mail.com> wrote in message
news:8b******** *************** ***@posting.goo gle.com...
I have the same problem.
Please help!
"Tim Marsden" <TM@UK.COM> wrote in message
news:<eI******* *******@TK2MSFT NGP11.phx.gbl>. ..
Hi,
I get the following dialog appear each time I open my VB.NET solution in
VS.NET 2003.
"The source control bindings for project xxxxx differ from those stored
in the solution file. Both sets of bindings must be the same."
This message appear for 2 of my 20+ projects in the solution.
I choose to use Solution bindings.
But when I reopen the solution the messages appears again.
I have tried unbinding and rebinding the problem project, but can't seem
to correct the problem.
Any comments would be appreciated
Tim