How do I fix the Visual Studio compile error, “mismatch between processor architecture”?

by

This warning seems to have been introduced with the new Visual Studio 11 Beta and .NET 4.5, although I suppose it might have been possible before.

First, it really is just a warning. It should not hurt anything if you are just dealing with x86 dependencies. Microsoft is just trying to warn you when you state that your project is compatible with “Any CPU” but you have a dependency on a project or .dll assembly that is either x86 or x64. Because you have an x86 dependency, technically your project is therefore not “Any CPU” compatible. To make the warning go away, you should actually change your project from “Any CPU” to “x86”. This is very easy to do, here are the steps.

  1. Go to the Build|Configuration Manager menu item.
  2. Find your project in the list, under Platform it will say “Any CPU”
  3. Select the “Any CPU” option from the drop down and then select <New..>
  4. From that dialog, select x86 from the “New Platform” drop down and make sure “Any CPU” is selected in the “Copy settings from” drop down.
  5. Hit OK
  6. You will want to select x86 for both the Debug and Release configurations.

This will make the warning go away and also state that your assembly or project is now no longer “Any CPU” compatible but now x86 specific. This is also applicable if you are building a 64 bit project that has an x64 dependency; you would just select x64 instead.

One other note, projects can be “Any CPU” compatible usually if they are pure .NET projects. This issue only comes up if you introduce a dependency (3rd party dll or your own C++ managed project) that targets a specific processor architecture.

More Related Contents:

  1. Is it possible to change the location of packages for NuGet?
  2. How do you share code between projects/solutions in Visual Studio?
  3. How exactly does the “Specific Version” property of an assembly reference work in Visual Studio?
  4. What does “exited with code 9009” mean during this build?
  5. Conditionally use 32/64 bit reference when building in Visual Studio
  6. XML – Data At Root Level is Invalid
  7. “The breakpoint will not currently be hit. The source code is different from the original version.” What does this mean?
  8. How to select different app.config for several build configurations
  9. HintPath vs ReferencePath in Visual Studio
  10. Getting the path of the current assembly
  11. Can I set Option Explicit and Option Strict on a Project/Solution level?
  12. Can I develop for .NET Framework 4 in Visual Studio 2008?
  13. Why is the Visual Studio 2015/2017/2019 Test Runner not discovering my xUnit v2 tests
  14. How do the .NET Framework, CLR and Visual Studio version numbers relate to each other?
  15. How can I read/write app.config settings at runtime without using user settings?
  16. Managed ODP.NET driver does not show up in Data Source dialog
  17. Browsing the .NET Framework source code from Visual Studio
  18. Can the DebuggerDisplay attribute be applied to types one doesn’t own?
  19. Web Services — WCF vs. ASMX (“Standard”)
  20. Are there any better ways to copy a native dll to the bin folder?
  21. How to Share App.config?
  22. Getting the PublicKeyToken of .Net assemblies [duplicate]
  23. Get the name of Enum value
  24. Developing .NET Compact Framework apps in Post-2008 Visual Studio?
  25. /LinkResource in Visual Studio 2010
  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