Version 9.4.1 Release has Started

Announcement: The release of Chilkat v9.4.1 has begun and will be ongoing for the next week. The Chilkat .NET assemblies for the 2.0/3.5, 4.0, and 4.5 Frameworks have been released and are now available. The release will continue over the next week until all supported programming languages, operating systems, architectures, etc. have been released.

Release notes will be available soon.

Following the v9.4.1 release, very-near term plans include:

1) Mono support for Windows, iOS, Linux, Android, etc. will follow. (Existing customers waiting for Mono pre-releases will be able to test prior to official release.) The Mono assembly should be usable within Xamarin.

2) The Windows Phone C++/CX wrapper generation is mostly complete. Support for Windows Phone 8 will be via a Windows Runtime Component. This will follow the Mono release.

3) Providing libs and assemblies for Windows Store (Metro) apps will follow. It requires an internal brain transplant for sockets and threading because Windows Store does not support the standard sockets and threading Chilkat currently uses internally. This needs to be implemented, and will take some time.

The located assembly’s manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

We want to use the 64-bit version of the Chilkat email functionality, but we get a could not load error message (see below for full error) when i use the v8.5.0 release of the Chilkat library. This also happens when i use the 32-bit version. Is it possible that the license key is linked to a specific version of the Chilkat library in our case version

If so how can we upgrade to 8.5.0, because we need to be able to install our software on a 64-bit machine.

Could not load file or assembly ‘ChilkatDotNet2, Version=, Culture=neutral, PublicKeyToken=eb5fc1fc52ef09bd’ or one of its dependencies. The located assembly’s manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

The .NET runtime requires that the assembly version matches exactly. The version of the assembly used in your Visual Studio project (i.e. on your development machine) must match the version deployed to your production system. The platform may be different: win32 vs. x64, but the version must match. The solution is to use Chilkat v8.5.0 in your Visual Studio development environment. New-version upgrades are always free, so you may download the latest at Chilkat Software Component Downloads