Hi Gary.
http://www.fsdeveloper.com/forum/threads/sbuilderx-error-on-update.430568/#post-6770283
Your quick View Plus isn't lying... Technically there are a few 32-bit dlls running. I've altered the headers to allow them to compile at runtime as 64-bit. So they are 64-bit, but their code is 32-bit. (That should really confuse everyone).
I used corflags for .Net 4.5 to reset the 32BITREQ flag as 0
That changes the requirement of the IL 'pseudocode' to compile at runtime as 64-bit... even though it was written as 32-bit.
I did this for a few dlls as I did not have the code to rewrite them as 64-bit.
The use of Program Files (x86) is a little foggy to me. It seems more of a hinderance than a help. But remember this is .NET, rather than a native exe. .Net compiles to IL, which is a sort of pseudo-code, and the IL gets recompiled at runtime by the JIT compiler. So truthfully, a .NET program is not an application at all. It's more of a script for the JIT compiler.
I don't know if natively compiled exe's run from the Program Files (x86)... but I suspect the folder is just a folder.
Dick