Problem with sharing projects across solutions

[jerseydude]

For the first time, after all these years of using vault, I am trying to place the same project in two solutions and I am having a problem.

Please reference the attached PDF file for screen snapshots.

I have a solution with 5 core libraries (HarrierGroupSolution) and an application solution with a number of application-related projects (ThirstyChickenSolution). I want to add the 5 core library projects to the application solution in addition to the library solution.

The first two existing projects (HarrierGroup & HarrierGroupSilverlight) seemed to add ok but the third one I tried (Reporting) is hosed. The files in the existing project show up with + signs next to them in Visual Studio and if add check in the solution changes after the add of the project, additional folders with a status of Missing get added in Vault under /HarrierGroupSolution.

Please help.

Thanks,
Mike

[lbauer]

What version of Vault are you using? What version of Visual Studio? It looks like you are using Classic Client integration, correct?

[jerseydude]

Linda,

Vault 5.0.3
Visual Studio 2010
SourceGear Vault Classic Client

Thanks,
Mike

[jerseydude]

Linda,

Any ideas on this problem? This is holding us up.

Thanks,
Mike

[lbauer]

How are you adding the library and reporting projects to the application solution? Are you doing an "add from source control" or "add an existing item" from disk?

[jerseydude]

Add Existing Project. How should I be doing it?

[lbauer]

I set up a test project and Add Existing worked with no problems. Add From Source Control worked, too.

In your case it looks like there may be some type of binding issue.

So -- a couple of ideas. Remove the Reporting project from the Application Solutions and try adding it from Source Control (File->Source Control->Add From Source Control.)

If that still doesn't work, unbind your Application solution/projects then use Add Existing project to add the Reporting Project. Then rebind using File->Source Control->Change Source Control. Bind the Reporting project first, then the other projects and bind the Solution file last.

Let me know if you have additional questions.

[jerseydude]

Linda,

Neither of those suggestions worked.

I tried re-binding the solutions but had no success.

I switched to the Enhanced client and this problem appears to be solved. Two things though:

1) Is the enhanced client recommended over the classic client?

2) I have a new funky behavior when I check out a file shared across projects in VS (Add Existing Linked File). After the check in, the linked file still shows as checked out. A get latest fixes it but this could be confusing. Linked files worked really well in the classic client.

Thanks again,
Mike

[lbauer]

The enhanced client is better in some ways, such as when you are trying to organize projects or create the proper bindings. There is also tighter integration with source control, like the Pending Change Set and Output windows. Line History is also available with the enhanced client in Visual Studio.

The Enhanced Client is different than the Classic Client, though. Not every feature in the Classic Client exists in the Enhanced Client.

The linked files check-in problem is a bug. It's logged as work item 12318 in our item tracking system. I will add your comments and bump it up in priority. The workaround is to check in files from the Vault GUI client.

[rwallacej]

I have been reading this thread. It says click
File->Source Control->Add From Source Control

I do not have this in Visual Studio or Vault. Please advise.

I have attached a VS Screenshot

Thank-you

[lbauer]

What version of Vault are you using?

What operating system is Vault/Visual Studio installed on?

If you look in Visual Studio under Tools->Options->Source Control->Source Control plugin, are source control options listed there?

[rwallacej]

Visual Studio 2008
Windows XP & 2003
Vault latest version - 5.0.4
Tools--Options displays the Enhanced Client

[lbauer]

Enhanced Client integration does not have the "Add from Source Control" function.

If you are using the Enhanced Client and you want to add an item that's already under source control, Get that project/file to disk (if it isn't already). Then in Visual Studio, right click on the solution or project you want to add to and select Add->Existing item, and browse to the location of the project you want to add. The files will be checked out and added.

[rwallacej]

Thank-you. I have tried this. The project can be successfully added to my solution (it appears after clicking Add Item)
However, after closing the solution and loading it again the following message appears
"The open from source control operation failed for the project XXXX. Close and reopen the solution and VS will attempt to reopen this project from source control."
The path XXX is correct; when visiting it in windows explorer I can open it. Not sure what is happening.

[lbauer]

How are you "loading the project" again. Are you opening it from disk or trying to Open from Vault?