Using regsvr32 to Register a 32-bit ActiveX or 64-bit ActiveX on Windows 64-bit System

A 64-bit Windows system has two separate registries — one for 32-bit processes, and one for 64-bit processes. The reason for this is simple: Let’s say your application instantiates an instance of an ActiveX component by calling CreateObject(“Chilkat.Ssh”). If your application is running in a 32-bit address space, the registry …

A .NET Assembly is *not* an ActiveX. It is not registered via regsvr32.

Question: I have now tried to register the component manually, but then I get his message: “The module c:\…\ChilkatDotNet2.dll was loaded but the entry-point DllRegisterServer was not found. Make sure that c:\…\ChilkatDotNet2.dll is a valid DLL or OCX file and try again.” Answer: A .NET assembly is not an ActiveX …

Incorrect Format Error when trying to load .NET Assembly

This Chilkat blog post explains the following error: “Could not load file or assembly ‘ChilkatDotNet2, Version=9.0.8.0, Culture=neutral, PublicKeyToken=eb5fc1fc52ef09bd’ or one of its dependencies. An attempt was made to load a program with an incorrect format.” When a DLL is loaded, it is mapped into the process’s address space. If the …

regsvr32 Problems

ActiveX components and controls have been around for many years.  Unfortunately, when regsvr32 fails to register a DLL, the only information provided is an error code.  Usually in the format of a 32-bit hex number, such as 0x80004005 (although not necessarily that particular error code, I simply picked one at …