Note: previous related travails are detailed here: http://stackoverflow.com/questions/18453917/why-am-i-getting-type-jro-jetengine-is-not-defined
I'm working on a legacy VB.Net app. If I stand in a certain position (on one leg, a la Ian Anderson, with right elbow akimbo and spasmodically flapping, a la Joe Morgan in his heydey at the plate) and breathe in LaMaze-like regularity, it will compile, but only grudgingly, as it furrows its brow and warns me:
*There was a mismatch between the processor architecture of the project being built "AMD64" and the processor architecture of the reference "Interop.JRO", "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.*
It had also been warning me, "*Possible problem detected while building assembly 'HDP': Referenced assembly 'JRO.dll' targets a different processor" but I squarshed that via Project > HDP Properties > Compile > Advanced Compile Options...> Target CPU > x86."*
On the project properties page, the Platform dropdown does not contian "x86" as an option. As mentioned, I can set it via the Advanced Compile Options... button, but now the page (Configuration > Platform) still says, "Active (x64)" (no x86 , only "Active (x64)", "Any CPU", "x64" and "All Platforms" are available).
So I have a mismatch between what the Compile page says, and what the "Advanced Compiler Settings" page says.
Why can't I just set it in one place, and have that value cascade through the project? For that matter, why doesn't Visual Studio guess which setting is best, based on DLLs in use, etc. (with the option to override its edumicated guess)?