Reputation: 13695
.NET version with 64-bit versus 32-bit assemblies
What version of .NET (64-bit vs. 32-bit) will be loaded if some of the assemblies referenced in an app are compiled with 32-bit only (instead of AnyMachine) setting? Will the app still run as 64-bit or will it be forced to run as 32-bit if at least one of the referenced assemblies is compiled as 32-bit only? The app is running .NET 3.5.
Upvotes: 4
Views: 642
Answers (2)
Reputation: 942478
The bit-ness is determined by the Platform Target setting on the EXE. There is no mechanism to ensure that a EXE that references a 32-bit only assembly will be forced to run in 32-bit mode as well. The assembly will simply fail to load with a BadImageFormatException.
If your program has a dependency on such a DLL then you must force the Platform Target on your EXE project from AnyCPU to x86.
Upvotes: 4
Related Questions
- Why do .NET developers offer 32-bit/64-bit versions of .NET assemblies?
- What are the differences between .NET in 32 or 64 bit systems?
- Differences between 32 and 64-bit .NET (4) applications
- Understanding 32-bit vs 64-bit in .Net
- Is there a difference between a 32-bit .NET application and a 64-bit .NET application?
- 64 bit vs 32 bit machine in asp.net
- why .net assemblies differ for different architectures?
- Difference between x86 and 64bit assembly in .NET
- 32bit vs 64bit performance
- .net console app 32 vs 64 bit