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

Question: When building my C# solution I get the following warning on several of the projects:   Severity Code Description Project File Line Suppression State Warning There was a mismatch between the processor architecture of the project being built “MSIL” and the processor architecture of the reference “ChilkatDotNet47, Version=9.5.0.75, Culture=neutral, …

Chilkat .NET Assemblies – Matching Visual Studio versions to .NET Framework Versions to VC++ Runtime Versions.

  The .NET Framework version that corresponds to each Visual Studio release is as follows: VS2017 — .NET 4.6, .NET 4.7 VS2015 — .NET 4.6 VS2013 — .NET 4.5 (actually 4.5.1, but we only care about major/minor numbers) VS2012 — .NET 4.5 VS2010 — .NET 4.0 VS2008 — .NET 3.5 …

Dynamically Loading .NET Assembly (32-bit or 64-bit)

Found a nice technique for dynamically loading a native .NET assembly and automatically choosing the appropriate one to match the loading process’s address space (32-bit or 64-bit). The source is located here: http://www.chilkatforum.com/questions/2966/why-separate-32-and-64-bit-chilkat-libraries-for-net and reproduced here: — I prefer another solution to this problem. It allows you to have a …