Wal - Approximation of actual:
Not that it matters, really, but . Not a menu (but it could be). The assemblies are DLL or standalone. Cooperative, but not open source projects, written by different people/teams, with less than rigorous and well-documented info. One app may want to run another, not knowing (at client end) what the OS bit-ness and the called applications compile mode is (since different compiles occur). But I also want to have more control than just catching exceptions - some of which - for the scenario I have outlined- are hard to predict. And, I learn a little more in the process. Regards, _____ Ian Thomas Victoria Park, Western Australia _____ From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Wallace Turner Sent: Wednesday, February 08, 2012 9:44 PM To: ozDotNet Subject: Re: Detecting what an assembly was compiled with >but there would be a problem if I started a process that was written for x64 only, in my x86 application, on a 32-bit Windows machine Is intriguing, so you have no clue if the process you're starting is x86 or 64 ? Why are you loading such a process? Do you have any control over said process? (is it yours, known third party or unknown) ?
