MDG Integration / different models and diagrams

[laanbroek]

Hi,

I am pretty new to UML and Enterprise Architect... so let's hope these are not ridiculous questions.

I have an open Visual Studio 2005 solution.
I open EA, create a new project, and choose for example Use Case Model, Data Model and Class Model.
I right click Class Model, choose Add-In, Connect External Project, Visual Studio.
I choose the project within the solution I want to use, and click Connect.
In the Merge Project dialog I leave Reverse, and under Import I select all my C# classes.
Now under a folder named after the namespace I indeed find all my classes.
I right click on that folder and choose New Diagam.
In the New Diagram Dialog I choose UML Structural and Class.
I select all my classes, drag them onto the diagram, and choose Paste Element as Simple Link for all.
In the main menu I choose Layout Diagram, and after that Save.
So... now I have a nice diagram.

Next I wanna try something similar for the Use Case Model.

Now it turns out that I can't connect it to my Visual Studio project as long as the Class Model is connected.

Question 1: Why is this? Why can I only connect one model type at a time?

So... I right click the Class Model and choose Add-In, Disconnect from Visual Studio.

So far so good, my classes and diagram are still there.

Now I connect the Use Case Model to my VS project.
And I select some classes from it.

Now it turns out that every class I added to the Use Case Model, disappears from the Class Model, and from the diagram. Without any warning.

Question 2: Why is this? Why can my classes only be in one model at a time?


Thanks
Ruud

[laanbroek]

Can somebody help here?
Is there a problem with the MDG Integration? Or am I understanding things wrongly?

Thanks
Ruud

[Paolo F Cantoni]

Can somebody help here?
Is there a problem with the MDG Integration? Or am I understanding things wrongly?

Thanks
Ruud

Yes, Ruud.  To a significant extent you ARE understanding things wrongly!

However, to another extent, I feel the basic design of the "integration" is BAD - "broken as designed".

If you search, you (should) find some commentary by me on the inability to handle multiple VS Solutions with overlapping componentry.

If you find my postings they MAY explain why you are experiencing the problems you are.

One thing you should get clear is that EA (correctly) sees a class file with the same in the same directory in different parts of the model as the same class. It thus will move things around as you see.

HTH,
Paolo
(Sorry I couldn't be more positive)

[Kevin G. Watson]

Hi Paolo... is this true of the new Beta (EA7 and MDG VS)?


I'm not a registered user so have gotta wait for public beta (or another client)

[Paolo F Cantoni]

Hi Paolo... is this true of the new Beta (EA7 and MDG VS)?


I'm not a registered user so have gotta wait for public beta (or another client)

Hi Kevin,

Not sure...  I finally found a partial work-around that worked for me and (as with all this sort of stuff in EA's unique interface) haven't dared deviate from it.  I'm now involved in other areas and that particular model set is in "hibernation".  But it may wake up soon...

Sorry I can't be more help...

Paolo