Experience with MDG link

[MikeGale]

I'm excited by the idea of MDG link.

Before I jump in I'd like some feedback on what others have found.

What is the experience of the early users of this product?

[bobwohler]

I've just started looking at it and I'm a "little" disappointed. I was expecting to see integrated menu options within Visual Studio .NET and there don't seem to be any. It's all from the EA side and in addition requires that the appropriate VS project be already open before it will recognize the integration. It seems to do what it's supposed to fairly well. I was just expecting something more. In my opinion, additional focus should be spent on creating an integrated EA designer for VS like most of the other UML vendors are doing (Borland, Rational, etc.). I would much prefer to work completely within VS. My two cents...

[ShimonSim]

I really hope that this is just a beginning. It seems to me that the add-in just provides more convenient way for forward and reverse engineering. Even though the Add-in helps a lot, to call it VS.NET integration is a little too much. Those who experience with VS.NET expect much more from the words "integrated with VS ".
Now, the process of merging drives me a little nuts.
1) The merge dialog just shows new classes in EA and VS but doesn't show classes that have been changed. There is no way to say there should we expect changes on method and variable level (and of cause you can't control that)
2) Deleting and renaming operations/attributes in VS and EA. Try it out once (and don't do it again). You will see that after merging you get two functions old and new in case of renaming and in case of deleting it comes right back (sorry)

So I really hope that this is only a beginning.
Just curious what EA's plans for it.
Shimon