Show Posts
1
Automation Interface, Add-Ins and Tools / MDA/MDG best practice
« on: June 23, 2006, 12:56:29 am »
Hi everybody
I am an EA newbie, and I have a "best practice" question. I have used EA to make the PIM, and that is now done, and I am now ready to start implementing. This will be done in VS 2005 using C#. I have bought the MDG Integration for VS 2005, as I was hoping to do most of the work from within VS 2005.
My first thought was to do an MDA Transform to a C# PSM, and then link the PSM pachages to my corresponding VS 2005 projects. But this would mean that the PIM would get out of sync as I did changes in the code and reverse engineered it back into the PSM. Is this a correct assumption?
In general then, what is "best practice" for working with MDA/MDG/VS 2005?
best regards
tab
I am an EA newbie, and I have a "best practice" question. I have used EA to make the PIM, and that is now done, and I am now ready to start implementing. This will be done in VS 2005 using C#. I have bought the MDG Integration for VS 2005, as I was hoping to do most of the work from within VS 2005.
My first thought was to do an MDA Transform to a C# PSM, and then link the PSM pachages to my corresponding VS 2005 projects. But this would mean that the PIM would get out of sync as I did changes in the code and reverse engineered it back into the PSM. Is this a correct assumption?
In general then, what is "best practice" for working with MDA/MDG/VS 2005?
best regards
tab