HMAC Hex Key Ambiguity

This happens all the time.. Quite often, a service provider will provide instructions for HMAC generation, and will provide a hexadecimal HMAC key in the example, such as: 01A0251D601FEF3305A38B124068A001CF3F099AA187DB2886314C67CDFDEBCD This is implicitly ambiguous because there are two ways to interpret the instructions: 1) The HMAC key is composed of the …

Hints for Minimizing Size of Windows CE 6.0 EXE in Visual Studio 2008

Chilkat continues to support (and will continue to support for many years to come) older development environments and platforms. The C++ lib for Windows CE (specifically for VS2008) is one such case. The size of the EXE in this environment can matter. Here is one customer’s helpful hints on how …

Chilkat Binary Encoding List

Throughout the Chilkat API there are method arguments and properties to indicate an encoding. These are encodings for binary data such as “hex”, “base64”, etc. Note: These are not character encodings. A character encoding, such as “utf-8” indicates the byte representation of a character. A binary encoding, such as “base64”, …

Mismatch between the processor architecture of the project being built “MSIL” and “AMD64”

For the following Visual Studio warning, see http://www.chilkatforum.com/questions/8087/mismatch-between-the-processor-architecture-of-the-project-being-built-msil-and-the-processor-architecture-of-the-reference-chilkatdotnet45-amd64 There was a mismatch between the processor architecture of the project being built “MSIL” and the processor architecture of the reference “ChilkatDotNet45”, “AMD64”. This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration …