The project file is not bound to source control, but the solution contains source control binding information for it.

Question

This may be more of a SQL Server Management Studio question, but I couldn't find a SSMS forum...

I've got a database solution that contains several projects.  They're just to keep track of changes to stored procedures, triggers, views, etc in a few databases I maintain.  There is a problem with two of the projects though.  No matter what I do, I can't seem to get them bound to source control right.  When I open the solution, I get:

The project file is not bound to source control, but the solution contains source control binding information for it.

With two options, use solution binding and remove solution binding.  If I keep the solution binding, everything works fine.  But it's really annoying to have to deal with every time I open the solution.  If I remove the solution binding, the projects are now unbound again.  If I try to fix them (using the change source control or Add Selected Projects to Source Control options under the File->source control menu), I just end up in the same situation.  I've even tried deleting the projects and re-creating them from scratch, then re-adding them to VSS.  If I open the solution files in a text editor I can see the SCC tags in every project, but these two.  Since I can't manually add the tags, and Management Studio itself only seems to want to bind them the wrong way, I'm getting really frustrated.

Can anyone point me toward a way to bind these so they work like the rest?

Answer 1

SQL Server Database Engine

http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=93&SiteID=1

 

 

Answer 2

Moved from SSIS forum

 

Answer 3

 

Got the stale message warning alert!  Still haven't found a solution.  Can anyone help?

Answer 4

 

I opened my project file up with wordpad and deleted the lines for source control.  This removed the opening error message, but some of my files still have a red line through them.

Answer 5

I had the same problem. It seemed like the project I added in SSMS wasn't properly adding source control binding information to the project file after binding it to source control. Manually adding the following lines at the bottom of the project file (in notepad, just before the </SqlWorkbenchSqlProject>) worked for me:

  <SccProjectName>SAK</SccProjectName>
  <SccAuxPath>SAK</SccAuxPath>
  <SccLocalPath>SAK</SccLocalPath>
  <SccProvider>SAK</SccProvider>

Answer 6

Paul's approach worked for me as well, although we are using TFS as our source control provider so I had to add something that looked more like this...

 <SccProjectName>$/. . . /My_TFS_Path</SccProjectName>
 <SccAuxPath />
 <SccLocalPath>.</SccLocalPath>
 <SccProvider>MSSCCI:Team Foundation Server MSSCCI Provider</SccProvider>

Answer 7

This is a common problem when you are using a shared location for source files.  User A opens the project and links it to F:\ProjectA\abc.  Then User B opens the project and cannot find F:\ProjectA\abc.

Each user needs to have a unique location for the source files downloaded from source control.

 

Answer 8

However, that does not appear to be the ONLY cause of the problem.  I am a single user and only using TFS2010 and SSMS2008R2.  My issue is that I wanted a solution file for each project so that they could managed independently, and a super-solution file that contained all projects, so that I could perform system-wide searches and cross-checks.

I solved the problem by:

1. Choosing the option to use solution binding, then

2. Adding another project to the solution.  This forced the re-write of the solution file.

3. Adding another script to the project.  This forced the re-write of the project file.

4. Checking in all changes.

5. Deleting the new script and the extra project,

6 Checking in all changes.

This appears to have solved the problem.

Answer 9

Not sure why Tom's answer is marked correct.  Watchman's answer worked perfectly for me.  Using VS 2012 and TFS 2012.  

Answer 10

THANKS, Watchman!  Elegant solution!  

FWIW, I tried just doing "save all" (Ctrl-Shift-S) at step #4, rather than checking in, and your approach still seemed to solve the problem.  So, if anyone's needing to minimize checkins- maybe just saving at step #4 will work.   Thanks AGAIN, Watchman- beautiful.