Ok, how about this: write a new .NET app, compile it as x86 and then reference the other app and manually invoke the Main() method on it? :-)
On Fri, Oct 21, 2011 at 5:05 PM, Stephen Price <step...@littlevoices.com>wrote: > No the 32bit shell launched from within a 64bit shell didn't seem to > work. I suggested running the 32bit shell from Start/Run but his shell > environment took ages to get up and running and he didn't seem keen on > that. (said it's the same thing anyway...) > The assemblies are signed too so guess that rules out the other option. > > Thanks for the reply! > > On Fri, Oct 21, 2011 at 1:55 PM, Joseph Clark <jcl...@atlassian.com> > wrote: > > I recall this coming up on the list recently (like in the last 6 months?) > > > > You can try: > > > > * Using the CorFlags tool to change the executable headers, but this will > > invalidate the assembly if it is signed. > > > > * Launch the app from a 32-bit console, which should only be able to > spawn > > 32-bit processes, I think... haven't tried this myself. > > > > > > On Fri, Oct 21, 2011 at 4:51 PM, Stephen Price <step...@littlevoices.com > > > > wrote: > >> > >> If you have a .Net app compiled as AnyCPU and want to force it to run > >> 32bit on a 64bit machine, is there a way to do that without a > >> recompile? > >> > >> cheers, > >> Stephen > > > > >
