login about faq

VS 2015 was issuing a warning when I compiled my project:

There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "ChilkatDotNet46, Version=, Culture=neutral, PublicKeyToken=eb5fc1fc52ef09bd, processorArchitecture=x86", "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project.

My solution includes three projects, (1) the main EXE, (2) a DLL, and (3) a test unit.

(1), the EXE, had "Platform target" set to "Any CPU" with "Prefer 32-bit" checked.

(2) and (3) were set to "Any CPU", but "Prefer 32-bit" was unchecked because it was disabled.

The EXE has a reference to "...chilkat-win32.", the 32-bit version of the library.

To avoid the warning, I changed Platform target to "x86" in all three projects. However, I'd rather use "Any CPU" with "Prefer 32-bit" checked to get the expanded address space that VS 2015 enables when "Prefer 32-bit" is checked. To use that, would we need a DLL for Chilkat that had /LARGEADDRESSAWARE?

asked Oct 10 '16 at 13:10

JohnnyCee's gravatar image


Starting in v9.5.0.62, to be released soon, the /LARGEADDRESSAWARE linker option will be used for the VS2015 .NET 32-bit build.


answered Oct 11 '16 at 08:53

chilkat's gravatar image

chilkat ♦♦

@chilkat - Good news! Thanks.

(Oct 11 '16 at 10:35) JohnnyCee

@chilkat - More good news. I checked back in today and found that v9.5.0.62 was released October 23. I did a nuget update and got v9.5.0.63, changed my project to "Any CPU" with "Prefer 32-bit" checked, and everything worked as expected. Thanks again.

(Nov 11 '16 at 16:59) JohnnyCee

@chilkat - Oops. Due to some issues unrelated to chilkat's DLL, I thought the processor architecture mismatch was gone when using v9.5.0.63, but I was wrong. The error message is still there if I change my project to "Any CPU" with "Prefer 32-bit" checked.

Is there a step I am missing?

(Nov 11 '16 at 20:33) JohnnyCee

Did you try the nuget package?

Instructions are here https://www.chilkatsoft.com/downloads_DotNet.asp

[Edit] Further looking at that, the instructions do tell you to use the Prefer 32-bit.


answered Oct 10 '16 at 14:22

TracyP's gravatar image


edited Oct 10 '16 at 14:26

@TracyP - I did use nuget to install Chilkat .NET.

(Oct 10 '16 at 15:03) JohnnyCee
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or __italic__
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported



Asked: Oct 10 '16 at 13:10

Seen: 393 times

Last updated: Nov 11 '16 at 20:33

powered by OSQA