Programming in EA and with EA - Add-In and C#

[carolin.boeckler]

Hello,

I created my own MDG Technology and I also programmed some Add-In (Extensions) for this Technology, I use Microsoft Visual Studio Express - C#.
I know that it is somehow also possible also to programm with EA. I never didi this yet.
Now my question:
Is it possible also to import the source code to the EAP file, where I write my MDG technology. And is it possible to compile the c# code in EA?
Does anybody have experiences with this?

Caro

[qwerty]

I guess, the answer is no. EA has build-in JScript and VB-Script. That's it. To bundle your compilation with an MDG you need to use some installer software.

q.

[Stefan Bolleininger]

Hi Carolin, (we met last year at the SparxRoadshow in Nürnberg)

The answer is yes and no :-)

You can get the code from VS express and import it into EA ->Then you can edit it or write new classes ->And then you can compile your c# code with you external compiler (Same scenario like mentioned below.)

The last idea of bundeling your code and the MDG to an installer might be funny.

If you are using an external installer like "win32_innosetup", copy your desired files into your "install_folder" and afterwards RUN the installer-application from inside an visual-script, jscript or action script.

In the sparxcommunity is some idea about it for importing libraries of document into the EA (I used it to import some SOP's and templates).

Here is the link:
http://community.sparxsystems.com/resources/scripts/importing-document-library-enterprise-architect

However this possibility is more then a workaround than an really good solution. The advantage i can see within is the storage of the complete Add-in data, MDG and configuration within ONE EAP-file.

To store it completely you will do something like that in your scripting

Precondition:

• Code for add-in supplied
• Installerfile supplied
• Scriptfile supplied
• VS C# express installed
• win32_innosetup application installed

1. Export the code to an temp location
2. adjust the installer file and export it (or the other way around)
3. create and export the information needed by the installer
4. create the MDG into the installer location
5. compile the code and save the binary to the installer location
6. run the installer and collect the new generated binaries location.


This might work- it should be worth a try  8-) 8-) 8-)

Regards

Stefan