The problem occurs if a 32-bit DLL (or executable) calls CoCreateInstance internally to instantiate the ActiveX in that case it fails because its looking in the 32-bit registry keys.
Indicates that your program attempted to load a win32 assembly on an beno cesar paraiso azul x64 Windows OS, or the reverse.
Copyright Chilkat Software, Inc.
Creative Commons.0 Attribution License.A 32-bit process must load the 32-bit ChilkatDotNet4.dll, and a 64-bit process must load the 64-bit ChilkatDotNet4.dll.Most computers will already have it installed.I installed the 64-bit version in addition to the 32-bit one in the GAC, and then the assembly loaded fine.It provides a managed API, but the inner core contains native code.Info, statistics 40,104 total downloads 2,710 downloads of latest version 26 downloads per day (avg view full stats.The registry in 64-bit versions of Windows is divided into 32-bit and 64-bit keys.If you write.NET application and target Any CPU, then it will run as a 64-bit application on an x64 computer, and therefore the x64 build of ChilkatDotNet2.dll would be required.NET Class Library (x64).I have tested the below suggestion locally which works perfectly however when I deploy my app to a test server I get the following error.(When adding the reference, Browse to the location of the ChilkatDotNet4.dll.).
2) If you really need to target Any CPU, then make sure to deploy the 32-bit Chilkat assembly w/ your app on 32-bit systems, and deploy the 64-bit Chilkat assembly to 64-bit systems.
It may be downloaded at: p, this is for the.0/3.5 (or greater) Framework. .
Copyright, copyright Chilkat Software, Inc.
Azure, Windows 10, Windows 8, Windows Server 2012, Windows 7, Vista, XP, 2003 Server, 2008 Server, etc.
Vista, and there turns out to be a separate GAC for 64-bit assemblies, and my application was searching there, and was not able to find the 32-bit.However, there is an issue (to be explained here) that requires the ActiveX to be built specifically for x64.Your project may select Any CPU for its target platform, but you must deploy the correct ChilkatDotNet2.dll to the target computer.There is no "install".3) If your app is running within T or a Windows Service and youre not quite sure whether its 32-bit or 64-bit, then install the 32-bit Chilkat assembly in the 32-bit GAC (Global Assembly Cache and also install the 64-bit Chilkat assembly into the 64-bit.The system cannot find the file specified.