EA 769 throws COM exceptions...

[Paolo F Cantoni]

Hi,

I just upgraded from 768 to 769 using the easetupfull file.  When I rebuild my automation application, it throws COM exceptions when I try to access Class connectors.    If I comment out the call to that method, the application runs to completion.

Since I'm new to C#, is there anything else I should have done?  Should I have regenerated references to EA?  I didn't reboot my machine.

When I restored 768, using its easetupfull it made everything good again.

Help!!!
Paolo

[sargasso]

Me too!  

I had weirdness on the 769 upgrade from the zip file.  No keys, add ins dont work,  paths lost,....  went back to 768 no probs.

BUT...

I am running (and installing) it over a win client for an "older" Fedora distn.  I put it down to that.  

Anyone else having 769 issues?

bruce

[thomaskilian]

I had talks with Sparx about wrong functionality using COM from scripting tools (Perl). And they confirmed having found some error to be corrected with 5.1. Maybe it has to do with that?

[Paolo F Cantoni]

Sparx suggested deleting and recreating the References to Interop.EA.dll (in the Sparx program folder), which I did.   Seems to have solved my problem.

This is probably a .Net specific problem.

Cheerz,
Paolo

[Marco Zapletal]

deleting and recreating references didnt help for me.

it also seems that the EA.Interop.dll has the same version (2.10.238.1) for both 768 and 769.

[Marco Zapletal]

i tried paolos solution again and it seems i made a failure before, because now it worked

thanks for the help,


marco

[Paolo F Cantoni]

i tried Paolo's solution again and it seems i made a failure before, because now it worked
thanks for the help,
marco

Now Marco, that's INTERESTING, because, as I wrote to Sparx, I'd already done what they asked.  But, on a hunch, I did it again - like you.  Worked the second time!

It's possible there may be some caching going on somewhere...

HTH,
Paolo

[Marco Zapletal]

imho i dont think it has something to do with caching - maybe it has something to do which 'version' of your addin dll is still registered and getting called when starting EA.

i am now using a tool called Regmon [http://www.sysinternals.com/Utilities/Regmon.html] to see what values are accessed in the registry (during EA startup) and thus i can see what addin.dll is actually called (you may use your addin name as a filter in regmon).

imho it has something to do with the interop functionality and registering for it...

regards,
marco

[Aaron B]

I just upgraded from 768 to 769 using the easetupfull file.  When I rebuild my automation application, it throws COM exceptions when I try to access Class connectors.  If I comment out the call to that method, the application runs to completion.

Hello All,

EA build 769 contained an accidental breakage in compatibility for the Automation Interface on EA.Connector.  This issue has been tracked down and resolved, and the fix will be released in the next few days in build 770.

Any developers who have compiled automation clients/addins using EA 769 will need to recompile against 770 when it is released.
If you have compiled against 768 or lower, your application should be fully compatible with build 770, but may be broken in 769 if accessing EA.Connector objects.

Release Notes for EA 5.0 build 770
*************************************
Fixed Automation Interface issue (introduced in 769), that caused EA.Connector interface to be incompatible with previous builds.
Note : Automation clients compiled against build 769 need to be recompiled against build 770.

We sincerely apologise for any inconvenience this may have caused.
If anyone has any further issues, please send us an email at [email protected].