RegAsm adding PrimaryInteropAssembly to wrong registry key

123 Views Asked by At

I am trying to regasm ADODB.dll in a docker container however whenever I run the command, the PrimaryInteropAssemblyName gets added to the "wrong" registry key (I say the "wrong" key but I am currently trying to learn how this witchcraft actually works).

Checking my own development PC, the PrimaryInteropAssembly name is added to: HKEY_CLASSES_ROOT\TypeLib{2A75196C-D9EB-4129-B803-931327F72D5C}\2.8

However in the docker container the PrimaryInteropAssembly name is added to: HKEY_CLASSES_ROOT\TypeLib{EF53050B-882E-4776-B643-EDA472E8E3F2}\2.7

The CLSID for v2.8 does exist, but the PIA Name value isn't added.

Can anyone shed any light on this?

0

There are 0 best solutions below