"Kevin Ortman" <KevinOrtman@discussions.microsoft.com> wrote in message
news:492A0C5A-69B5-4845-8E5F-6CCA77926303@microsoft.com...
> How does the 64Bit CLR handle .NET Framework 1.1 assemblies in the
> following
> scenario?
>
> App.exe <--- .NET Framework 2.0 100% Managed
> MyLib.dll <--- .NET Framework 1.1 100% Managed
> App.exe has a dependecy on MyLib.dll.
>
> Does the whole application execute in 64-bit native?
> Does the whole application ( or only the 1.1 assemblies ) execute in
> WOW64?
>
> Also, is there a way to verify how if the code is running in 64-Bit native
> non-programatically? ( other than the task manager )
>
> Thanks,
> Kevin Ortman
>

"Phil Wilson" wrote:

> It's my understanding that 2.0 assemblies running 64-bit mode will not link
> to 1.1 assemblies, basically because the loader can't assume that the 1.1
> assembly will work correctly in 64-bit mode, so it errs on the side of
> safety. I think this is still valid:
> http://blogs.msdn.com/junfeng/archive/2004/08/11/212555.aspx
> --
> Phil Wilson
> [Microsoft MVP-Windows Installer]
>
> "Kevin Ortman" <KevinOrtman@discussions.microsoft.com> wrote in message
> news:492A0C5A-69B5-4845-8E5F-6CCA77926303@microsoft.com...
> > How does the 64Bit CLR handle .NET Framework 1.1 assemblies in the
> > following
> > scenario?
> >
> > App.exe <--- .NET Framework 2.0 100% Managed
> > MyLib.dll <--- .NET Framework 1.1 100% Managed
> > App.exe has a dependecy on MyLib.dll.
> >
> > Does the whole application execute in 64-bit native?
> > Does the whole application ( or only the 1.1 assemblies ) execute in
> > WOW64?
> >
> > Also, is there a way to verify how if the code is running in 64-Bit native
> > non-programatically? ( other than the task manager )
> >
> > Thanks,
> > Kevin Ortman
> >
>
>