Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Aaron B

Pages: 1 ... 53 54 [55] 56 57 ... 59
The Add-In needs to be registered with the system (i.e. using regasm.exe), and also needs to have an entry in the local registry to tell EA to look for it (e.g. [HKEY_CURRENT_USER\Software\Sparx Systems\EAAddins\<Addin Name>]).  If a user does not have rights to modify the registry, it may not be possible to properly install the Add-In.

From memory, .NET DLL's get registered with regasm.exe, not regsvr32.exe.  In either case, you shouldn't need to manually run this to do debugging.  In your VS project, make sure that "Register for COM Interop" is enabled (I think this is usually under the Build options).

Automation Interface, Add-Ins and Tools / Re: EA Lite & Plugins
« on: November 26, 2008, 11:51:38 am »
Try reading the Repository.EAEdition property. Values should correspond to the EA.EAEditionTypes enumeration.  I believe EA Lite reports a value of -1.

Automation Interface, Add-Ins and Tools / Re: Getting the linked item
« on: June 27, 2008, 03:32:10 pm »

1) First, you need a reference to the Element you are interested in.
2) Loop over the Element.Connectors collection
3) Check the Connector.ClientID and Connector.SupplierID values.  These are ElementID values for the objects at each end of the connector.  One of these will refer back to your first element, and the other will refer to the related element.
4) With the ElementID obtained above, use Repository.GetElementById() to retrieve a reference to the related element.


I would highly recommend that you run newAttribute.Update() before your create the new tagged value.  When creating a new object through automation, always run the object's Update() method before attempting to add anything to it's collection properties.

So something more like...

Code: [Select]
EA.Attribute newAttribute = (EA.Attribute)elContainer.Attributes.AddNew("MyAttribute", "");

EA.AttributeTag attrTag = (EA.AttributeTag)newAttribute.TaggedValues.AddNew("TagName", "");
attrTag.Value = "TagValue";



".vbp" files are project files, not source files.  ".bas" files can be imported by EA 7.1.  In Tools | Options, try setting the Import File Extensions setting for Visual Basic to ".cls;.frm;.ctl;.bas;".  See Visual Basic Options.

The only way to synchronize with a project file is by using something like our MDG Link Add-Ins (E.g. MDG Link for Visual Studio).  Unfortunately though there is no MDG Add-In for VB6 projects.

Last I knew on the subject, EA Automation would not work running as a service.  Not sure of the exact reason however.  I am not aware of anyone sucessfully running EA Automation from a windows service.

NB: When instantiating a new EA.Repository object, it needs to start an 'EA.exe' process to interface with.  It would appear that perhaps it is failing to start this process.

Just in addition to Simon's comments - MDG Link for Eclipse should work under Linux.  MDG Integration for Eclipse does not.  Please make sure that you are installing the correct Add-In.

No idea.  I'm not aware of any development on this at the present time.

I'm not aware of any way to stimulate commands from the EA menus at this time either.  Maybe through some SendKeys commands if you were desperate, but I probably wouldn't recommend it. ;)

Unfortunately it is not possible to create a custom dockable window or toolbar for an Add-In at this time, however you can create a custom ActiveX control within a new tab (sharing with the diagram pane).  This is done via the Repository.AddTab() method.  For more information, see:

Edit: Sorry, I just noticed from the end of your last post that you already seem to be aware of this.  Regardless, this is the only way to embed a custom interface within the EA window at this time.

Try calling Repository.AdviseElementChange(ElementID).  This should refresh most common EA windows where the specified element may appear.


The Floating License mechanism used by Enterprise Architect is proprietary and is not compatible with other floating license management systems at this time.  We have had requests to support other third-party license servers (such as FlexLM) but there is no development towards this at the present time.

Automation Interface, Add-Ins and Tools / Re: Element Keywords
« on: December 18, 2007, 02:53:04 pm »
For an element of type "Package", you can find the corresponding package ID in the MiscData(0) field.  I never actually realised that the same guid is used for both the Element and Package, but yes, looking up the package based an the element's GUID also seems to work.  Either way, you do need to call GetPackageByID or GetPackageByGUID to retrieve the EA.Package object.

Keywords should be available from the MiscData(4) field.

Automation Interface, Add-Ins and Tools / Re: Generate EA GUID
« on: December 11, 2007, 02:32:11 pm »
GUID values are automatically generated if you are adding new items via the Automation Interface.  If you are directly inserting into the database, you would need to use a Windows API call like CoCreateGuid to generate a valid GUID for you to insert.


There is a demo under the Resources area of our website showing how to associate TFS Work Items with elements in your EA model.  No idea whether it's exactly what you're after, but might be of some help at least.

See the "Team Foundation Server" demo on the following page:

Pages: 1 ... 53 54 [55] 56 57 ... 59