x86 and x64.NET Frameworks on the same x64 Machine

[Malcolm Mackay]

I have a Windows Server 2003 R2 x64 and am wanting .net framework 2.0 32 bit
for a 32 bit app. It already has x64 .net framework 2.0 installed. Why
when I try and install x86 .net framework do I get:
Error: Cannot install on a 32-bit operating system

 

[Pavel Minaev]

I have a Windows Server 2003 R2 x64 and am wanting .net framework 2.0 32 bit
for a 32 bit app.  It already has x64 .net framework 2.0 installed.  Why
when I try and install x86 .net framework do I get:
Error: Cannot install on a 32-bit operating system

That's because you do not need it. If you have alread installed
the .NET x64 runtime, you actually get both x64 and x86 versions. The
one that will be used for your application depends on which platform
it advertises in the assembly (it's the /platform compiler switch for
C# and VB). For AnyCPU, it will use x64; otherwise, it will use
whatever was specified.

 

[sloan]

Loosely related, but perhaps a sign of "proof".

Here is a comment:
http://www.dotnetjunkies.com/WebLog/nenoloje/archive/2008/05/11/468257.aspx


For those who want to access a JET database on x64, the workaround is to
build the code against the x86.
Then the JET stuff will then work. There is no JET provider for x64.

I have a Windows Server 2003 R2 x64 and am wanting .net framework 2.0 32
bit
for a 32 bit app. It already has x64 .net framework 2.0 installed. Why
when I try and install x86 .net framework do I get:
Error: Cannot install on a 32-bit operating system

That's because you do not need it. If you have alread installed
the .NET x64 runtime, you actually get both x64 and x86 versions. The
one that will be used for your application depends on which platform
it advertises in the assembly (it's the /platform compiler switch for
C# and VB). For AnyCPU, it will use x64; otherwise, it will use
whatever was specified.