CODEWITHSUNDEEP
c#.netvb.netvisual-studiovisual-studio-2010
Erx_VB.NExT.Coder
Erx_VB.NExT.Coder

Reputation: 4856

Can you install .NET Framework Client Profile 32 bit version on a 64 bit PC/OS?

Mainly I ask this because I don't want to distribute both versions, and if I need to instal a 64bit .NET on an x64 PC and a 32bit .NET on a 32 bit PC then I would need to make this check in my loader application to download the correct version for the correct PC.

However, if I just do a one for all, it would be easier - and i would just like to know if theree is anything I should know before doing this (ie: any repercussions?) or all good?

Also, when I compile an exe in a 64bit version of VS2010 does it compile a 32bit exe by default or a 64bit? I'm presuming 32, but just wanted to make sure.

Thanks.

Upvotes: 2

Views: 5349

Answers (2)

Mikael Svenson
Mikael Svenson

Reputation: 39695

If you target AnyCPU for your compilation, the app will run as 64bit on a 64bit OS, and 32bit on a 32bit OS. If you target x86, the app will run as 32bit regardless of the OS. If you target x64, the app will only run on a 64bit OS.

The 64bit version of .Net also includes the 32bit dll's.

If you have to install the runtime from the Internet, then use the web installer. It will take care of downloading and installing the correct version on the client. This way you can target AnyCPU (or x86) and be certain that the app will run regardless of the OS.

If you need to package .Net with your app, download the full file which has both 32/64bit versions included - http://download.microsoft.com/download/9/5/A/95A9616B-7A37-4AF6-BC36-D6EA96C8DAAE/dotNetFx40_Full_x86_x64.exe

Client profile web install

Client profile full install

Silent install can be done with the /q parameter and you might want to add /norestart as well and handle reboot yourself if necessary.

Check out this blog post and the MSDN documentation on what switches are available.

Upvotes: 5

Hans Passant
Hans Passant

Reputation: 942000

The .NET bootstrapper automatically installs both the 32-bit and the 64-bit versions of the .NET framework on a machine with a 64-bit operating system. Nothing you have to do to tell it to do so. Avoid distributing the .NET framework yourself, you'll have a hard time keeping up with the security updates. Just tick the option in the Setup project's Prerequisites to get the bootstrapper, that will download the latest and greatest during install on the target machine, if necessary. The option is automatically ticked when you create an installer for a managed program.

There is no 64-bit version of VS2010, no need to worry about that.

The Platform Target setting in the Project + Properties, Build tab for your EXE project is relevant. It defaults to x86 in a project that was created from scratch in VS2010. There is no great reason to change it to AnyCPU for the Release build unless you need the extra virtual memory space that a 64-bit process can provide. If you do change it then do make sure to test it thoroughly. I know you've been tinkering with unmanaged COM servers, x86 is probably a hard requirement.

Upvotes: 3

Related Questions