I am in a situation where a client now has developers on board, and I have to colaberate with them - however my internal projects are on my Vault server, and theirs are on their Vault server - but I can't seem to get it to work like that?
Is it possible in one solution to have projects under two different source control sites?
Two Vault Servers in one solution?
Moderator: SourceGear
Re: Two Vault Servers in one solution?
I don't believe we've run across that before. Unfortunately, I don't think it will work, because a single Vault client can't be connected to two servers at the same time. However, if you don't modify their projects (just your own), you might be able to set up a different solution file that only has your projects bound to source control.Dino wrote: Is it possible in one solution to have projects under two different source control sites?
If you want to explore other workarounds, take a look at the MSSCCPRJ.SCC files underneath each bound project - they contain the connection information relevant to that project or solution. I don't think simply editing the files to go to different servers will work though.
If you do need to modify projects on both servers, perhaps you could maintain two solutions files, hopefully mapped to the same working folders. In one solution you would be bound to your server, and in the other, be bound to the other server, and you would use the appropriate solution when making modifications to each project?
These are just ideas - I don't know if they will work. Let us know if you find a good solution, in case any one else has these requirements.
Dan,
The problem I have is a bit compounded - I have a client who now has a developer who is working with me, and so they wanted access to their source code - my suggestion was for them to install Vault on their site, and thus their developer and I could access it.
I already have 2 versions of the solutions and projects, because the solution has about 30 projects, but only 12 of which are theirs, and the other 18 are my internal support libraries which their developer won't have. So one copy of the solution/projects references the DLLs, and one references my projects - but as you know, the internal projects (which are in Vault on my server) are not being handled when I have the full solution open.
Not a major I don't think - I can open another solution to edit those projects anyway... was just a thought. Now realising I should have got my client to install their source code on my server, and then I could have just restricted their access to my source... oh well.
The problem I have is a bit compounded - I have a client who now has a developer who is working with me, and so they wanted access to their source code - my suggestion was for them to install Vault on their site, and thus their developer and I could access it.
I already have 2 versions of the solutions and projects, because the solution has about 30 projects, but only 12 of which are theirs, and the other 18 are my internal support libraries which their developer won't have. So one copy of the solution/projects references the DLLs, and one references my projects - but as you know, the internal projects (which are in Vault on my server) are not being handled when I have the full solution open.
Not a major I don't think - I can open another solution to edit those projects anyway... was just a thought. Now realising I should have got my client to install their source code on my server, and then I could have just restricted their access to my source... oh well.