Use own Add-Ins via the Automation Interface

[DKL9]

I have written an Add-In DLL (“myEAfunctions.dll”) using C# and deployed it by creating a key value “EAAddins” in the registry, as described inside the EA-Help. The Add-In provides me some functions I could call over Menu Items and some functions I could call from a MDA Transformation (“myTransformation”) by using the command %EXEC_ADD_IN. So long, everything works fine!

Now I am trying to call the MDA Transformation “myTransformation” from outside the EA by using the command Project.TransformPackage of the Automation Interface (Interop.EA.DLL). This does not work!

I have no problems to call Built-In transformations like “Java”, “JUnit” or own written, as long they are not jumping into the Add-In via %EXEC_ADD_IN.

It looks like the Automation Interface (Interop.EA) does ignore the registry-Key “EAAddins” and does not load the myEAfunctions.dll.

Is this an EA-Bug? Has anybody fixed it?

[«Midnight»]

You might be using an obsolete method of loading MDG technologies.

First, you should have your MDG Technology executable file in the EA add-ins path, just as you would if you were expecting the file to load by hand. You can also use the new Repository (or is it Project) method to load the technology. Note that you should make sure your documentation file is fairly recent - last 6 months or so - and avoid those methods that are marked as obsolete.

If you're still in the dark search the forum for MDG Technology and load and I'm sure you'll find additional pointers.

HTH, David

[Eve]

I can confirm that EA doesn't load add-ins when opened from automation.  You'd have to submit a feature request for it.