Addin Error 0x80040154 with EA15.1

[Guillaume]

Hi,

A client is moving to EA15.1 on Windows 10 PCs and found that one of its addins no longer works -> Error - Missing (0x80040154).
I did a bit of investigations with Adrian's EA Inspector
- no error found on this addin (listed as green in EAInspector)
- comparing with eaUtils which runs fine, I noticed that the addin in error is built with .Net runtime v2.0.50727, not v4.0 -> this seems to be the issue.

From other posts, it seems that the addin DLL is not properly registered so I ran a regasm "path to dll\my.dll" /codebase
I get the following error:
RegAsm : error RA0000 : Impossible de charger le fichier ou l'assembly 'Interop.EA, Version=2.10.238.1, Culture=neutral, PublicKeyToken=d28e1c76302f6a17' ou une de ses dépendances. Le fichier spécifié est introuvable.
.. which means it cannot load 'Interop.EA, Version=2.10.238.1' or one of its dependencies.

I tried to run regasm both from C:\windows\Microsoft.NET\Framework\v4.0.30319 and C:\windows\Microsoft.NET\Framework\v2.0.50727
Could it be that .Net 2 and .Net 4 have separate lists of registered DLLs?

Any idea on how to fix this?

Thanks,
Guillaume

[Geert Bellekens]

Have you tried installing .Net framework 3.5?

That is not standard installed with Windows 10 (I need that for things like ArrayLists in scripts)

Geert

[Uffe]

Hi Guillaume,

If you're registering the assembly manually, don't you have access to the source code for the offending Add-In?
In which case, just rebuild it targeting a more recent version of .NET. 2.0 is waaay past end of life.

/Uffe

[Paolo F Cantoni]

Hi Guillaume,

If you're registering the assembly manually, don't you have access to the source code for the offending Add-In?
In which case, just rebuild it targeting a more recent version of .NET. 2.0 is waaay past end of life.

/Uffe

As I discovered recently!  The, untouched for more than a decade, AddIn I'm updating had elements of .NET v2 in it.  Took me a little while to track down and replace.

Paolo

[Uffe]

Hi Guillaume,

If you're registering the assembly manually, don't you have access to the source code for the offending Add-In?
In which case, just rebuild it targeting a more recent version of .NET. 2.0 is waaay past end of life.

/Uffe

As I discovered recently!  The, untouched for more than a decade, AddIn I'm updating had elements of .NET v2 in it.  Took me a little while to track down and replace.

Paolo

Just to make life more interesting, the lifecycles for .NET platforms do not follow simply from the version numbers. Oooh no.
So .NET Framework 3.5 is still being supported, but 4.0 and 4.5 are not. 4.5.1 is not, but 4.5.2 is. But that's all to do with how Microsoft decided to bastardize the .NET version numbers in order to confuse the enemy.

Here's a handy page and here's the same only brieflier.

/U

[Guillaume]

Thank you for your answers.
The client won't be able to install anything I'm afraid (based on Geert's suggestion to install 3.5).
I don't have access to the addin src code but I asked the editor if he could try to rebuild it with .NET 4+

Is this issue due to the Interop.EA.dll file that was built on .Net 2 until EA 14, and a more recent version after?