Project Binding - What Happened? => SOLVED

[M4]

VERSION: 3.0.5 (2833)

Solution File (under scc), 17 Project Files consisting of: 1 DB Project, 1 c# Web Project, a couple console projs, 1 winform proj, and the rest library projects.

Today I added the 18th Project, C# Console application. The steps to produce my situtation were as follows:

Steps Produced Error:
------------------------------------------
1. Added new project to solution.
2. Checked in new project
3. Closed VS.NET 2003 IDE
4. Open VS.NET 2003 IDE

Errors:
------------------------------------------
DIALOG 1: Title: Source Control; Message: The source control binding information has been removed for project [PROJECT NAME]. The project will be opened without source control. [OK][HELP]

DIALOG 2: Title: Microsoft Development Environment; Message: The project [PROJECT NAME] is under source control. An error occurred registering this project with source control. It is recommended that you do not make any changes to this project. [OK]

Please let me know what I should do to resolve.

Regards,

Reed
------------------------------------------------------------
SOLUTION:
------------------------------------------------------------
I removed my local solution file and all project files
from my local pc. I setup my solution again locally,
got latest from vault, and everything is now working
as exptected again. I hope this saves some of you
the 6 hours I wasted on this problem.

[dan]

I would suggest going into Change Source Control, and attempting to bind the project again to the location you just added it to in Vault.

Did adding the project require checking out the solution file too? If so, did it checked back in as well?

[M4]

Ok, this is really frustrating. I was able to delete the project I added that mucked this all up, and rollback the solution file.

Great, so I'll try again I thought..BAM! Same thing. I used a different project name. The project I'm adding is binding fine, but the last project in the solution is now unboud and the settings under "Change Source Control" say:

[PROJECT] | <No Sever> | <No Server> | UNCHECKED | Not Controlled

Funny thing to is that *ALL* my projects say: "<Unable To Display>" beneath the Sever Binding column.

When I try to "REBIND" the unbound project, the project shows connected but the status is <Invalid>

This really bites. Any other suggestions? We are dead in the water until this gets going 90% of our work is being done in our web project, which is broken right now.

Thanks,

Reed

[dan]

You should be able to continue with the old projects if you don't checkin the solution until the new project is binding correctly.

You might try this a different way: Add the project to source control by itself (not part of the solution). If that succeeds, then invoke "Add project from source control" and see if that produces better results for the solution file (if it can then recognize all the projects).

Is there something different about this project, like if you are logging in with a different user, or trying to put it in a different repository or server?

[M4]

Ok, so I tried created a seperate project, added the proj to source control. Then opened my solution added project from source control.

All the same behavior exists ... again. Same problem, nothing different. Any other suggestions?

[M4]

I also must say I checked the pathing in the sln file, its all correct.

[M4]

No, there is nothing different in this scenario. We've added projects all the time, now its just failing. My user acct has admin priv. so I don't think its a permissions thing. We're going to the same server we always have.

Please help. Thx.

[dan]

There isn't a lot of info here to go on, other than it doesn't bind. Try turning on IDE logging (See http://support.sourcegear.com/viewtopic.php?t=2898) and see whether that reveals anything.

I can try to reproduce this here if you are able to send the solution. Does it have the same problems regardless of which machine you try to add the project from?

[M4]

Dan,

You (sourcegear) realize this happens to several people. I'm afraid what I'm going to have to do is rebuild our entire solution from ground up, consider losing all history and begin again. This would be quite painful for us. To give honest feedback, these are the exact (no answer) problems we had with VSS which caused us to consider Vault and buy it.

Have you been able to produce the same issue in your labs?

[dan]

1. Did the log reveal any info?

2. Can you send me the solution so I can try to reproduce this here?

[dan]

Another thing you could try is to rebuild the solution file itself by adding in each project from source control. You wouldn't lose any project history that way, and you could then checkin the solution file on top of the existing one and no history would be lost.

[M4]

Dan,

I tried upgrading to 3.0.6 and it didn't work either. An interesting peice of information I have about this problem is I had my partner add the project from his computer and it added just fine so could this be a problem with my PC? I will be out most of the day today but will try again this evening. I am going to try to rebuild my local solution files/directories and I'll report my finding.

Reed

[dan]

Binding is an association between local folders and repository folders, so it is definitely possible there is a problem with the local folders on one machine that don't show up on other machines.

It would be good to compare the contents of the solution/project files that work on your collegue's machine against the ones that are not working on your own.