Using MDG Link with Version Control

[Martin Terreni]

You better work with EAP also, so you can work off line, I don't think it is possible with DB.
SO you better put all your root modules->views->packages under VC with stubs so every one openning it (both from DB or EAP) will see the project.
It has a "little" issue though - when working with EAP you need to check out the packages to trigger->"get latest", and by this I mean each and every package, since using stubs only saves the structure for the higher nodes. I think we'll have to develop a script to solve this EA problem (and it IS an EA problem).

another thing - all in all - EA is the toll with the best ROI in the market BY FAR!

[CleverCoder]

Our goal is to allow a developer to get a working copy, open a solution, work on some code, and quickly create and maintain diagrams related to the code.  Putting the EAP file on a file server would add a nasty dependency..  All in all, the DB based project seems to be the way to go.  Setting up version control isn't completely transparent (maybe a new release of EA will link and include the libraries needed to use Subversion without the need for a separate executable)... but the setup is simple enough that things are good.

I've been instructed to talk to the person responsible for purchasing about the upgrade to Corporate. This is good news.

I'm still frustrated that it took such extensive testing to determine the correct configuration.. and I'm still surprised that the MDG Link marketing / support team didn't have more detailed documentation on how we might want to setup EA with a version controlled codebase (am I crazy?). Maybe toss them white papers and include this valuable fact in the documentation..  I feel that the product documentation should have this information.. rather than having to scour the forums or read 'whitepapers'. I digress.

Thanks for all the help. Maybe this will help the next person.

Cheers!
-Sean