Sharing projects in multiple solutions

[MattK]

In advance, I have read the FAQ and could not get this to work. Here's what I'm trying to do:

I have several class library projects, we'll call them A, B, and C that I want to share with two solution files, say, solution X and solution Y. All of these projects and solutions are already added to Vault 4.1.2 in their own folders.

Without source control, what I normally do on my localhost is add project A, B, and C to solution X via right clicking on the solution and choosing add existing project, and the same with project Y.

How do I do this with Vault? How do I add a class library project A, already in Vault, to a solution X? I have tried using the Share feature, which worked, but it created a separate working folder on my localhost and downloaded all of the files again. I then have to check for the latest version in Solution Y continuously.

I tried "Add Existing Project" from Solution X to add project A. What happens is that anytime I edit one of the project files from Solution X, I get warnings from visual studio if another solution is open that has the same project stating that the file has been modified outside of the current working environment, which is true.

How do all the .NET developers deal with this issue? It seems rather much like a fundamental one.

Many thanks!

[Beth]

Normally, I would still recommend the sharing idea. Then what happens to one folder in Vault gets automatically applied to the other folder as well. You shouldn't ever need to go back to the other one to see if something changed, unless you are meaning that you changed something on disk, and Solution X was not updated from Vault. Is that the case here?