Version Control and Packages

[BillShiley]

I am an EA newbie, and I am trying to figure out how to effectively use our version control system (Visual Source Safe) with EA.  I have put the project under version control, and have separated it into multiple packages, each of which is controlled and under version control.  Generally, it seems to be well-integrated.

The reason for this setup is to allow multiple team members to work on parts of the model simultaneously.  However, if EA prevents me from establishing a generalization link from an element of a package that is checked out to an element of a package that is not checked out.  This is a problem if one of the packages contains general framework classes that are used by elements in other packages.  I am not really trying to modify the contents of the package, I am just trying to use them.  Is there any way around this problem?

The other problem is what to do with the project (.EAP) file itself.  I thought I understood the help file to say that we could keep all of the packages under version control, and let each user have his own project file.  However, if I create a new project file, commands like GetPackage are disabled until I put the NEW project under configuration control.  How do I go about importing all of my packages into the new project?

Thanks,

Bill