MDG Use with Multiple Projects

[eAndy]

I have a VS.nET solution with 3 projects.

They all share a common root name space. SC.Platform.

I have the following package hierarchy in EA
SC
- Platform
- Business
- Data
- BPC

and once connected to VS.NET want the following pacakage structure in EA ( implies that there are a lot more projects that I want to hook up but I'm focusing on the 3 project solution dealing with SC.Platform for the purposes here)

SC (root)
- Platform
     - Common ( SC.Platform.Common.CSPROJ)
     - WebUI ( SC.Platform.WebUI.CSProj)
     - WebControls (SC.Platform.WebControls)
- Business
     - BnO (SC.Business.BnO)
     - Accounting (SC.Business.Accounting)
- Data
     - BnO (SC.Data.BnO)
     - Accounting (SC.Data.Accounting)
- BPC
     - BnO (SC.BPC.BnO)
     - Accounting (SC.BPC.Accounting)

problems:
1. when I connect one of the projects in the solution to the EA model I the connect button is disabled and I can't connect the other projects in the solution to the EA Model. And unless each project in teh solution has to be connected to a different pacakage in EA I can't see how multiple projects will work. If each project has to be linked to a separate package in EA and the tool is going to do what I list here in #2 I'm screwed. It will create such a crappy structure it will be unusable. I'm hoping I'm wrong here on either account.
2. When a project is connected to the SC.Platform package in EA, the tool re-creates the SC.Platform packages under the package where its connecting so I end up with SC.Platform.SC.Platform.Common instead of it realizing that its already under SC.Platform and just creating the Common package under where its connecting.
3. when working in a team will the links to vs.net projects be maintained on other team members machines as long as they have the projects in the same places on their drives?

i think this tool has a lot of potential. It appears that some simple scenarios are given in the documentation to get the product out. It would be really nice if the some advanced scenarios could be detailed.

We have a large project and plan to use db repository with controlled pacakage for pushing things back and forth to remote teams. I'd love to see this work but having some trouble and questions right now.

Any help is appreciated.

Thank you

[Phil_Bachmann]

OK it's 6 months late, but at least you got a reply  

Re 1 & 2:

The problem essentially occurs because we gave no thought to multiple projects that were part of the same namespace hierarchy.  In the short term there is nothing for it but to live with the fact that your model is comprised of duplicate packages for ancestor namespaces eg.

We have discussed the matter at Sparx and concluded that perhaps you should be allowed to connect to a Solution as well as a VS Project (just as an Eclipse package might connect to a workspace rather than a project).  This idea seems feasible and we are looking at implementing it some time in the future.

Regarding question 3 - the answer is no.  Each workstation needs to be set up to connect to the individual projects.

Regards,

Phil Bachmann
Sparx Systems

[rene.titulaer]

Phil,

do you have any idea when this functionality will be implemented. We are evaluating EA in combination with MDG link and we are quit happy with it but we need the functionality to connect to multiple projects. Without this functionality MDG link isn't a proper solution for enterprise projects.

Regards,
René