Shared Repositories

Tom · Post by **Tom** » Tue Jun 28, 2005 2:17 pm

Hi:

I have a VB6 project that is bound to one repository but several BAS modules are common across multiple repositories. So for these common BAS moduels, I as the Vault Admin placed them in a different repository.

I thought that if I (the Vault Admin) gave my developers read/write access to both repositories, that my developers would be able to (a) open up the VB 6 project and edit code in either repository.

Well, I found out that this is not the case. The files in the shared repository are not accessible. The error I get when I try and open one of these shared BAS modules is as follows.

File v:\\vb6\Common Modules\modSharedFunctions.bas is not valid for this operation.

Can anyone assist or tell me how I can share common modules across multiple projects? Or is this just not possible?

Thanks

Tom

Note: V is a shared network drive.

lbauer · Post by **lbauer** » Tue Jun 28, 2005 3:25 pm

It doesn't work -- at least we haven't been able to get it to work. One user had reported they had a project with files in more than one repository, but then they found that Visual Studio kept trying to create new folders in one repository for files that were in another repository, etc. It just got confused.

All files for a project should be in the same repository.

Tom · Post by **Tom** » Wed Jun 29, 2005 6:09 am

Can you please add this to your enhancement list. Surely this has been brought up by other Vault customers, or are we the first?

While we like the concept of separate repositories, we wish we could share common functionality across multiple projects! This way we have one single version of the truth and a central place to manage code changes.

Other than copying the common files to each project, can you give me any additional advise?

Tom

lbauer · Post by **lbauer** » Wed Jun 29, 2005 9:47 am

Surely this has been brought up by other Vault customers

We do have a feature request logged for the ability to move/copy files and folders across repositories. For now, we suggest users follow these guidelines:

http://support.sourcegear.com/viewtopic.php?p=5183

Getting VS.NET integration to work properly across repositories would be still be challenging. I'll log that as a request as well. Of course if any users have gotten this to work, we'd like to hear from you.

For now, we suggest you make copies of the files you need for each repository.