Project file not binding correctly to source control

[Graham Binner]

We are using Visual Sourcesafe 2005 together with SQL Server 2008 Management
Studio.

We have a SQL Server solution which is checked into Sourcesafe and contains
multiple projects. Whenever I open the solution, I get the following error
message:

"The project file myprojectfile.ssmssqlproj is not bound to source control,
but the solution contains source control binding information for it.
Do you want to open the project using source control binding information
from the solution or open it as unbound and fix the solution file?"

The message gives the options of "Use Solution Binding" and "Remove Solution
Binding". I always select "Use Solution Binding". This appears to work, but
the next time I open the solution, the error message reappears.

We also have the same issue when using SQL Server 2005.

Any help would be appreciated.

[Catherine]

You may select the "Remove Solution Binding" option and try re-binding
the solution and projects to SourceSafe through menu File->Source
Control->Change Source Control.

Thanks.

Catherine Sea
www.dynamsoft.com

[Binner@discussions.microsoft.com Graham Binner]

Thanks for your reply. I tried your suggestion. Although it appears to
successfully rebind the solution, I get the same problem after I close the
solution and then attempt to reopen it.

[Graham Binner]

Thanks for the reply. I tried your suggestion. I did find that the problem
project file was missing the 4 lines that you mentioned. I copied and pasted
the lines from a project that is working correctly.

Unfortunately I now get the following message whenever I open the project in
the SQL Server Management Studio;

"There appears to be a discrepancy between the solution's source control
information about some project(s) and the information in the project file(s).

To resolve this discrepancy it will be necessary to check out the project
file(s) and update them. If the check out fails, however, and the solution is
closed without saving, you will see this warning again the next time you open
the solution."

Puzzling. I'll investigate further.

"Dan" wrote:

> This is a bit of a hack and I'm working in SQL 2005 but it works:
>
> If you open the .ssmssqlproj file in a text editor for a project that is
> correctly binding you'll find 4 lines at the bottom of the file that
> reference the source control bindings (all starting with Scc). Copy those 4
> lines from the correctly bound project, then check the problematic projects
> out fo SourceSafe and then paste those 4 lines into the problematic project
> file. When you then open the solution in SQL Server Management Studio it
> will now be correctly bound and you can check the changes into Source Safe.

[bbe...@gmail.com]

We have 2 solutions and hundreds of projects.

I migrated from VS 2008 SP1 to VS 2010 SP1 and was also receiving the error:

There appears to be a discrepancy between the solution's source control information . . .

I would open solution1, allow it to update the projects, then open solution2, only to get this error again.

I analyzed the solution files and found the following:

Root Cause:

solution1.sln and solution2.sln files are inconsistent with each other in regards to the project source control bindings.

Example:

solution1.sln

SccProjectUniqueName6 = Project1\\Project1.csproj
SccProjectName6 = \u0022$/Project1\u0022,\u0020HSBAAAAA
SccLocalPath6 = Project1

solution2.sln

SccProjectUniqueName6 = Project1\\Project1.csproj
SccLocalPath6 = .
SccProjectFilePathRelativizedFromConnection6 = Project1\\

Solution:

I fixed this issue by manually modifying the solution files to be consistent in notepad. I copy and pasted the source control info from solution1.sln into solution2.sln for projects they had in common.

I eventually wrote a small utility to automate this.

https://github.com/bentoo/MergeSolutionSourceControl