Addins on EA v16 beta 64 bit

[Geert Bellekens]

I just installed the v16 beta, and found that my add-ins are no longer visible.

I'm guessing that is because of the 64 bit part.

The manual unfortunately doesn't tell me how to install a add-in on a 64 bit installation.: https://sparxsystems.com/enterprise_architect_user_guide/16.0/automation/deployingaddins.html

I'll try some stuff if I find the time, but some documentation would be nice.

Geert

[Takeshi K]

Hi Geert,

We need to add an entry to:

HKEY_CURRENT_USER\SOFTWARE\Sparx Systems\EAAddins64
or
HKEY_LOCAL_MACHINE\SOFTWARE\Sparx Systems\EAAddins

for 64bit EA.

HTH,

[Geert Bellekens]

HKEY_LOCAL_MACHINE\SOFTWARE\Sparx Systems\EAAddins64
Seems to work in getting EA to notice there is an add-in, but I get "Error - Missing (0x80040154)" for each of them.

These add-ins do work in the 32 bit version. Any tips?

Geert

[Takeshi K]

Hi Geert,

If you use VisualStudio, please check whether CPU setting of the project is 'AnyCPU', not 'x86'.


Or, another possibility, you need to register by the following RegAsm. (if yours are .NET add-in)

C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegAsm.exe

HTH,

[Sunshine]

HKEY_LOCAL_MACHINE\SOFTWARE\Sparx Systems\EAAddins64
Seems to work in getting EA to notice there is an add-in, but I get "Error - Missing (0x80040154)" for each of them.

These add-ins do work in the 32 bit version. Any tips?

Geert

I've installed the 64-bit version of Sparx EA too on Windows 11 just to make it exciting.
I noticed that Office Integration MDG was missing.
Tried reinstalling but no luck.
Then tried adding Reg entry manually and got same error message.
Is there going to be a new Office Integration MDG released so its compatible?

[Eve]

Yes there will be a new release of Office Integration. There may be a new version of Office Integration before we add 64 bit support to it. That decision hasn't been made yet.

[Geert Bellekens]

Yes there will be a new release of Office Integration. There may be a new version of Office Integration before we add 64 bit support to it. That decision hasn't been made yet.

I was really hoping to get a hint from a Sparxian regarding the addins for v16 64 bit.
Do I need to send in a a bug report?

Geert

[Geert Bellekens]

Changing the <PlatformTarget> in the .csproj files from "AnyCPU" to "x64" solved the issue for my add-ins.
I though AnyCPU would work for any CPU (both 32 + 64 bit) but apparently I was wrong.

The annoying thing is that now my add-ins won't work on v15.2 (32 bit); Hmmm,  Need to figure out a good way to handle this

Geert

[Sunshine]

Changing the <PlatformTarget> in the .csproj files from "AnyCPU" to "x64" solved the issue for my add-ins.
I though AnyCPU would work for any CPU (both 32 + 64 bit) but apparently I was wrong.

The annoying thing is that now my add-ins won't work on v15.2 (32 bit); Hmmm,  Need to figure out a good way to handle this

Geert

That doesn't line up with my understanding either so that sucks.

As a work around you might have to resort to doing two builds for 32 and 64 bit.

[timoc]

Yes there will be a new release of Office Integration. There may be a new version of Office Integration before we add 64 bit support to it. That decision hasn't been made yet.

Will the new addin still require the Microsoft office interoperability package to be installed beforehand?

[Eve]

Changing the <PlatformTarget> in the .csproj files from "AnyCPU" to "x64" solved the issue for my add-ins.
I though AnyCPU would work for any CPU (both 32 + 64 bit) but apparently I was wrong.

The annoying thing is that now my add-ins won't work on v15.2 (32 bit); Hmmm,  Need to figure out a good way to handle this

I've seen the reverse before, where AnyCPU wouldn't load in 32 bit. I suspect the problem is that the register for COM Interop within Visual Studio only does one. Try explicitly registering the other way.

[Ian Mitchell]

I just noticed that the set of Addins I have loaded - LemonTree, eaDocX and Model Expert, all see to appear OK in v16 beta1. Not that this helps you, but I'm pretty sure that I haven't done anything clever to make mine work in the 64-bit world...

[Geert Bellekens]

Thanks for the input. I'll investigate further.

Geert

[Helmut Ortmann]

Hello,

with VS2019 and WIX I can build, debug and run my AddIns for x86 and x64. Two WIX/VS installation projects which refer to the same code, the same WIX file definitions, compiled and build to x86 or x64. The work is doing VS2019 and WIX. EA loads the x86 or the x64 Addin. You may install both at the same time.

The differences are:
- Target x86/x64, settings in VS/WIX
- Change the path to the registration of AddIn
- Installation folder to distinguish x86/x64
- Give the Wix output in the two WIX setup-projects, a different name (MyAddin.msi and e.g. MyAddin64.msi)

The procedure:

• Make a configuration for x64
• Make a new WIX Setup-Project for x64
• I copied the existing and modified the project GUID (new) and the X86 entry to X64, giving the installation project a new name
• Changed the installation folder to "MyFolderX64" or so
• Replaced the EA Add-In registration by EAAddins64, instead of EAAddins
• Build for the target environment (x86 or x64/li]
  
  
  In near future, I release hoTools x86 and x64 on GitHub. Feel free to have a look in GitHub or ask questions.
  
  Best regards,
  
  Helmut

[Geert Bellekens]

Thanks Helmut, looking forward to your update on Github so I can piggyback on that

Geert