Groups | Blog | Home
all groups > visual studio .net general > september 2005 >

visual studio .net general : The solution appears to be under source control, but its binding information cannot be found


Bill Cohagan
9/26/2005 9:52:21 AM
I'm running VS.Net 2003 (7.1.3088) under Windows XP MCE. I'm getting this
error on several projects when I try to open them. This is a relatively new
computer so it's possible I haven't actually opened these projects since
building the system and restoring these project files from a tape backup.
I've seen a blog entry on this suggesting I rebind the solution to VSS, but
after this error (and a couple more) during startup there are no VSS related
menu entries available with which to try the fix.

Here's the complete text of the message:
=========
The solution appears to be under source control, but its binding information
cannot be found. It is possible that the MSSCCPRJ.SCC file or another item
that holds the source control settings for the solution, has been deleted.
Because it is not possible to recover this missing information
automatically, the projects whose bindings are missing will be treated as
not under source control.
=========

The next error text:
=========
The project Setup.vdproj appears to be under source control, but no source
control provider is installed on this computer. Source control integration
will be disabled for this project.
=========

The final error text:
==========
Some of the properties associated with the solution could not be read.
==========

Another possibility is that I've just installed VS 2005 RC1; however I'd
think Google would have produced more hits if this were the culprit. So,
anyone know the cause/fix for this problem?

Thanks in advance,
Bill

Kevin Spencer
9/27/2005 7:25:35 AM
[quoted text, click to view]

I run into this problem frequently, as I often VPN to my work machine and
copy projects or update files on my home machine from the work machine, and
my work machine uses a LAN SourceSafe database, while my home machine uses
its own local SourceSafe database. In addition, we have a graphics guy here
who occasionally needs updates which I copy directly to his machine.

I have found that it is possible to re-bind a project which has been
"corrupted" in this way to an existing SourceSafe database, as long as the
SourceSafe project has the same folder/file configuration, and the same file
names in it. I do this by removing all binding information from the
project/solution in Visual Studio.Net, and then binding it to the existing
SourceSafe project. From time to time it is also necessary to re-synchronize
the code, by checking an item out of the SourceSafe project without updating
the local file, or by adding a new file into the SourceSafe database. All of
this can usually be done from within Visual Studio.Net.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
I'd rather be a hammer than a nail.

[quoted text, click to view]

Bill Cohagan
9/27/2005 8:55:43 AM
Gary
These files were backed up from the old machine, then restored to the new
machine. On both the old and new machines I was referencing the same VSS
database (on another machine on the LAN.) So, the VSS *is* there (and I can
open the VSS client on the new machine with no problems.) Also, the
MSSCCPRJ.SCC file is in fact there on the new machine.

I can't "rebind" the project/solution because there is no [Source Control]
menu item on the File menu. The blog seems to be oriented towards "cleaning
up" a copied project that is no longer under source control. In my case it
IS (or should be) under source control -- so I just want to restore that
functionality. I don't understand how this can happen. I'm hoping I don't
have to edit all those files in EVERY project on the new machine!!

Any suggestion as to how I should proceed?

Thanks for the response,
Bill


[quoted text, click to view]

v-garych NO[at]SPAM online.microsoft.com (
9/27/2005 9:01:14 AM
Hi Bill,

[quoted text, click to view]

Based on the error message, it appears those problematic projects which you
restored from the tape backup were under a source control system before, so
at this point, do you have that related/original source control system
installed/connected in your current machine? If you don't have the original
source control system which those projects used to be belonged, I am afraid
you could not rebind the solution to the VSS again, you may ignore this
message or add these projects to source control as a new item.

By the way, do you mentioned the blog entry as the following one, which has
a useful discussion on this issue:

Error: Visual Studio project or solution appears to be under source
control, but isn't...
http://blogs.msdn.com/korbyp/archive/2003/12/17/44209.aspx


Thanks!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no rights.
Bill Cohagan
9/27/2005 10:07:01 AM
Gary
It occurred to me that a "simple way" to solve this problem might be to
simply recreate the on disk folder structure via a "get latest" from VSS.
So, I deleted the old folder and did the get latest, creating the new
folders as necessary. Sadly when I load the solution file I get the same
message. Note that this project/solution works fine on another machine.

It seems to me that if one is unable to do this via VSS then there is
something fundamentally wrong. I've got VS.Net set up to use VSS as the
source control provider. What could be causing this problem?

Bill

[quoted text, click to view]

CT
9/27/2005 12:26:51 PM
Bill,

If you can't or don't want to rebind to the VSS database, here's a solution
for you:
http://community.integratedsolutions.dk/admin/blogs/posteditor.aspx?App=visual_studio_.net_2003&PostID=215

--
Carsten Thomsen
Enterprise Development with VS .NET, UML, AND MSF
http://www.apress.com/book/bookDisplay.html?bID=105
Communities - http://community.integratedsolutions.dk

[quoted text, click to view]

v-kevy NO[at]SPAM online.microsoft.com
9/28/2005 5:55:31 AM
Hi Bill,

Could you let me know how you backup the VSS database? Using the VSS backup
wizard, or just copy the projects?

You can try to delete the local folder again and in the VS.NET, select
File/Source Control/Open from source control to open the solution. If the
VSS server cannot be bound during openinig, you can just disconnection all
the projects from the server. HTH.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."
Bill Cohagan
10/2/2005 12:17:17 AM
Kevin
Actually, although the Source Control menu item is on the File menu, all
the SC items are disabled. What might be causing that?

Thanks,
Bill

[quoted text, click to view]

Kevin Spencer
10/2/2005 8:22:46 AM
See if the following KB article helps:

http://support.microsoft.com/default.aspx?scid=kb;en-us;305106

If not, check your Tool|Options|Source Control settings.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
Big things are made up of
lots of little things.

[quoted text, click to view]

Bill Cohagan
10/2/2005 1:32:30 PM
Kevin
The KB article doesn't help because Step 5 tells me to use a menu
selection that is disabled in my menu. Checking VS2003's Tool|Options\Source
Control settings I find that things look "right"; i.e., Visual Source Safe
is specified. Any other suggestions?

Bill

[quoted text, click to view]

Bill Cohagan
10/2/2005 1:47:20 PM
Kevin
Problem solved! I reinstalled VSS and now everthing seems to be working
normally.

Thanks for the response in any case.

Bill

[quoted text, click to view]

Kevin Spencer
10/3/2005 7:41:58 AM
Sorry I couldn't be more help. I certainly don't like to have to resort to
that sort of tactic, although it sometimes works. Next time (hopefully
never!) you might try a Repair instead of a re-install.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
Big things are made up of
lots of little things.

[quoted text, click to view]

AddThis Social Bookmark Button