Conditionally use 32/64 bit reference when building in Visual Studio

by

Here is what I’ve done in a previous project, which will require the manual edition of the .csproj file(s). You also need separate directories for the different binaries, ideally siblings of each other, and with the same name as the platform you are targeting.

After adding a single platform’s references to the project, open the .csproj in a text editor. Before the first <ItemGroup> element within the <Project> element, add the following code, which will help determine which platform you’re running (and building) on.

<!-- Properties group for Determining 64bit Architecture -->
<PropertyGroup>
  <CurrentPlatform>x86</CurrentPlatform>
  <CurrentPlatform Condition="'$(PROCESSOR_ARCHITECTURE)'=='AMD64' or '$(PROCESSOR_ARCHITEW6432)'=='AMD64'">AMD64</CurrentPlatform>
</PropertyGroup>

Then, for your platform specific references, you make changes such as the following:

<ItemGroup>
  <Reference Include="Leadtools, Version=16.5.0.0, Culture=neutral, PublicKeyToken=9cf889f53ea9b907, processorArchitecture=x86">
    <SpecificVersion>False</SpecificVersion>
    <HintPath>..\..\Lib\Leadtools\$(CurrentPlatform)\Leadtools.dll</HintPath>
  </Reference>
  <Reference Include="Leadtools.Codecs, Version=16.5.0.0, Culture=neutral, PublicKeyToken=9cf889f53ea9b907, processorArchitecture=x86">
    <SpecificVersion>False</SpecificVersion>
    <HintPath>..\..\Lib\Leadtools\$(CurrentPlatform)\Leadtools.Codecs.dll</HintPath>
  </Reference>
  <Reference Include="Leadtools.ImageProcessing.Core, Version=16.5.0.0, Culture=neutral, PublicKeyToken=9cf889f53ea9b907, processorArchitecture=x86">
    <SpecificVersion>False</SpecificVersion>
    <HintPath>..\..\Lib\Leadtools\$(CurrentPlatform)\Leadtools.ImageProcessing.Core.dll</HintPath>
  </Reference>
  <Reference Include="System" />
  <Reference Include="System.Core" />
  <Reference Include="System.Data.Entity" />
  <!--  Other project references -->
</ItemGroup>

Note the use of the $(CurrentPlatform) property, which we defined above. You could, instead, use conditionals for which assemblies to include for which platform. You could also need to:

  • Replace the $(PROCESSOR_ARCHITEW6432) and $(PROCESSOR_ARCHITECTURE) with $(Platform) to consider ONLY the target platform of the projects
  • Alter the platform determination logic in order to be appropriate to the current machine, so that you’re not building/referencing a 64 bit binary to execute on a 32 bit platform.

I had this written up originally for an internal Wiki at work, however, I’ve modified it and posted the full process to my blog, if you are interested in the detailed step-by-step instructions.

More Related Contents:

  1. Targeting both 32bit and 64bit with Visual Studio in same solution/project
  2. C# compiling for 32/64 bit, or for ‘Any CPU’? [duplicate]
  3. How can I determine if a .NET assembly was built for x86 or x64?
  4. Nuget connection attempt failed “Unable to load the service index for source”
  5. How exactly does the “Specific Version” property of an assembly reference work in Visual Studio?
  6. What does “exited with code 9009” mean during this build?
  7. How do I run Visual Studio as an administrator by default?
  8. “The breakpoint will not currently be hit. The source code is different from the original version.” What does this mean?
  9. Release generating .pdb files, why?
  10. Favorite Visual Studio keyboard shortcuts [closed]
  11. Getting the path of the current assembly
  12. Change C++/CLI project to another framework than 4.0 with vs2010
  13. Remote machines cannot connect to Visual Studio web server
  14. Can I load a 32 bit DLL into a 64 bit process on Windows?
  15. How can I read/write app.config settings at runtime without using user settings?
  16. How to prevent Visual Studio from launching WcfSvcHost.exe while debugging?
  17. Can Visual Studio 2012 be installed side-by-side w/ Visual Studio 2010?
  18. What is app.config for?
  19. Can the DebuggerDisplay attribute be applied to types one doesn’t own?
  20. Access x86 COM from x64 .NET
  21. How do I find the stack trace in Visual Studio?
  22. Open .net framework 4.5 project in VS 2022. Is there any workaround?
  23. How to Share App.config?
  24. Getting the PublicKeyToken of .Net assemblies [duplicate]
  25. How to fix DNX/DNVM in Visual Studio 2015?
  26. How do I attach Visual Studio to a process that is not started yet?
  27. Visual Studio CPU High Usage
  28. Visual Basic Capture output of cmd
  29. Visual Studio popup: “the operation could not be completed”
  30. Managing complex Web.Config files between deployment environments

Leave a Comment