Shared model in TFS

[Geert Bellekens]

We have following setup:
One repository (sql server database) with the model for department1
One repository (als sql server) with the model for department2
One model that is shared by the two department, this model resides in both repositories.
This shared model is the only one that is version controlled in TFS.
This setup works pretty good, I can checkout a shared package in any of the two repositories, edit it and check it back in. After such a change i can do a get Latest and I can see the latest version of the package in the other repository.
The problem i have is with the function "Re-sync all statusses with VC providers". If I have checked-out a package in dep1 repository and I perform this function in dep2 repository it sets the vc status of the package to checked-out, and it allows me to check it back in from the dep2 repository.
That is of course NOT the desired behaviour since this will wipe out all changes I was making in dep1 repository. This is a very dangerous situation to have.
I was thinking I could possibly solve this by having two seperate local folders for my version controlled files, but it looks like that is not possible with TFS.
Does anyone have an idea on how to solve this?

Thanks

Geert

[HowardB]

Hello Geert,

TFS will allow you to have any number of local working copy folders associated with a given Project folder.  You just need to create a new TFS workspace to define the mapping for each new local working folder.

However, this won't help you, because EA requires that ALL access to any given package file (by ALL users and from all models) is done using a VC Configuration that has the same UniqueID that was originally used when the package was added to version control.  (This requirement is stated in the EA User Guide.)  On any PC, a given VC Configuration can only reference a single working copy path.


We have an additional "Resynch Status" function (targetted for inclusion in EA version 8.0) that operates on just the selected package, rather than every package in the model.  That might be more suitable for your purposes.


Best regards,
Howard.