VS 2015 was issuing a warning when I compiled my 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-win188.8.131.52.60libnet461ChilkatDotNet46.dll", 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
Starting in v184.108.40.206, 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
This does not work as described with 220.127.116.11. Compilation targetting "Any CPU", regardless of which of the two assemblies is used to compile with, yields this warning:
C:Program Files (x86)MSBuild14.0binMicrosoft.Common.CurrentVersion.targets(1820,5): warning MSB3270: There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "ChilkatDotNet46, Version=18.104.22.168, Culture=neutral, PublicKeyToken=eb5fc1fc52ef09bd, processorArchitecture=AMD64", "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.
This shows up regardless the runtime-mode selection ("Prefere 32-bit"), which is irrelevant during compilation, but mentioned in case somebody gets tempted to ask.
answered Feb 22 at 08:11