What's the difference between different Build Configuration settings
e.g. Any CPU, Mixed Platform, WIN32 etc in Visual Studio.
相关问题
- How to know full paths to DLL's from .csproj f
- Importing NuGet references through a local project
- Visual Studio 2019 - error MSB8020: The build tool
- 'System.Threading.ThreadAbortException' in
- VS2017 RC - The following error occurred when tryi
相关文章
- How to show location of errors, references to memb
- How to track MongoDB requests from a console appli
- Visual Studio Hangs on Loading UI Library
- How to use Mercurial from Visual Studio 2010?
- Build errors of missing packages in Visual Studio
- Copy different file to output directory for releas
- Edit & Continue doesn't work
- “Csc.exe” exited with code -1073741819
The build configuration names don't mean very much - they proliferate if you have C++ and C# projects in the same solution (and even worse if you have mobile projects too), because the various types of projects use different configuration names, so you end up with lots of them.
We try to keep deleting all the configurations we're not using, but that's hard work sometimes as often when you add a new project, unwanted configurations will be added back to the solution.
My recommendations is to decide on what configurations you need (by looking at the actual settings within them), and then remove everything else.
As other platform already explained. (i.e. X86 for 32 bit, x64 is for 64bit only, and 'Any CPU' can run in Both). I'll concentrate on
Mixed Platform
and how this different fromAny CPU
.The
Any CPU
is at the project level setting, where as in real world solution we have number of projects under one solution, and their are chances that some of my project useAny CPU
, but others uses thex86
orx64
build platform.So at solution level automatically
Mixed Platform
will be selected. this indicates that during Build/Rebuild solution each project build based on their selected platform.From: this post. https://social.msdn.microsoft.com/forums/vstudio/en-US/81c72e8b-6335-4bf4-b7c0-b5c322edcaee/mixed-platforms-vs-any-cpu
Here's a link that helps explain the build configuration setting found in Visual Studio and its build files:
http://visualstudiohacks.com/articles/visual-studio-net-platform-target-explained/http://web.archive.org/web/20151215192101/http://visualstudiohacks.com/articles/visual-studio-net-platform-target-explained/
Basically the setting states what platform the assembly is able to run on. When AnyCPU is selected, the resultant DLL is marked as able to run anywhere; when x86 is selected, the resultant DLL is marked as only being able to run on 32-bit systems and will not run in 64-bit applications or processes (but will run in 64-bit Windows;) and so on and so forth.
This just sets flags on the compiled DLL - it does not change other aspects of compilation process at all.