General Property Page (Project)
The new home for Visual Studio documentation is Visual Studio 2017 Documentation on docs.microsoft.com.
The latest version of this topic can be found at General Property Page (Project).
When you right-click on a project node in in Solution Explorer, and select Properties, the General property page under the Configuration Properties node in the left pane displays two sections of properties:
The properties in the General section affect the location of files that are created in the build process and which files to delete when the Clean option (Build menu) is selected.
Specifies the platform that the project will run on. For example, Windows, Android, or iOS. The value Windows 10 means the project targets the Universal Windows Platform. If you are targeting earlier versions of Windows, the version is not listed and the value in this field appears as just Windows. This is a read-only field that is set when you create a project.
Target Platform Version
For the Windows platform, specifies the version of the Windows SDK that your project builds with. For Windows, this is the Windows SDK version. Visual Studio 2015 ships with Windows SDK 8.1. If you installed the Tools for Windows 10, each version of those tools that you have installed appears in the dropdown.
To target Windows 7 or Windows Vista, use the value 8.1, since Windows SDK 8.1 is backward compatible to those platforms. In addition, you should define the appropriate value for _WIN32_WINNT in targetver.h. For Windows 7, that's 0x0601. See Modifying WINVER and _WIN32_WINNT.
You can install the v110_xp platform toolset included in Visual Studio 2012 to use the current version of Visual Studio to build Windows XP and Windows Server 2003 projects. For information on how to obtain and use this platform toolset, see Configuring Programs for Windows XP. For additional information on changing the platform toolset, see How to: Modify the Target Framework and Platform Toolset.
Target Platform Min. Version
Specifies the lowest version of the platform that the project can run on. This property appears only if the project type supports it, such as in Windows Universal projects. If your app can take advantage of features in a newer Windows SDK version, but can still run on earlier versions without those features, perhaps with some loss of functionality, then the value of these two properties might be different. If so, your code should check the version of the platform it is running against at runtime and not try to use features that aren't available in older platform version.
Specifies the directory where tools such as the linker will place all final output files that are created during the build process. Typically, this includes the output of tools such as the linker, librarian, or BSCMake.
To programmatically access this property, see OutputDirectory.
Specifies the directory where tools such as the compiler will place all intermediate files created during the build process. Typically, this includes the output of tools such as the C/C++ compiler, MIDL, and the resource compiler.
To programmatically access this property, see IntermediateDirectory.
Specifies the file name this project generates.
Specifies the file name extension this project generates; for example, .exe or .dll.
Extensions to Delete on Clean
The Clean option (Build menu) deletes files from the intermediate directory where a project's configuration is built. Files with extensions specified with this property will be deleted when Clean is run or when you perform a rebuild. In addition to files of these extensions in the intermediate directory, the build system will also delete any known output of the build regardless of where it is located (including intermediate outputs such as .obj files). Note that you can specify wildcard characters.
To programmatically access this property, see DeleteExtensionsOnClean.
Build Log File
Allows you to specify a non-default location for the log file that is created whenever you build a project.
You can use project macros to change the directory location. See Common Macros for Build Commands and Properties.
Allows the project to target a different version of the Visual C++ libraries and compiler. Visual C++ projects can target either the default toolset in Visual Studio 2012 (v100) or the toolset that creates executables that can run on Windowx XP.
The properties in the Project Default section represent default properties that you can modify. The definition for these properties can be found in the .props files in Installation Directory\VC\VCProjectDefaults.
There are several configuration types from which to choose:
Application (.exe), displays linker toolset (C/C++ Compiler, MIDL, Resource Compiler, Linker, BSCMake, XML Web Service Proxy Generator, custom build, prebuild, prelink, postbuild events).
Dynamic Library (.dll), displays linker toolset, specifies /DLL linker option, and adds the _WINDLL define to CL.
Makefile, displays makefile toolset (NMake).
Static Library (.lib), displays librarian toolset (same as linker toolset except substitute librarian for linker and omit XML Web Service Proxy Generator).
Utility, displays utility toolset (MIDL, custom build, prebuild, postbuild events).
To programmatically access this property, see ConfigurationType.
Use of MFC
Specifies whether the MFC project will statically or dynamically link to the MFC DLL. Non-MFC projects can select Use Standard Windows Libraries to link to various Win32 libraries that are included when you use MFC.
To programmatically access this property, see useOfMfc.
Use of ATL
Specifies whether the ATL project will statically or dynamically link to the ATL .DLL. If you specify anything other than Not Using ATL, a define will be added to the compiler's Command Line property page.
To programmatically access this property, see useOfATL.
Defines whether _UNICODE or _MBCS should be set. Also affects the linker entry point where appropriate.
To programmatically access this property, see CharacterSet.
Common Language Runtime support
Causes the /clr compiler option to be used.
To programmatically access this property, see ManagedExtensions.
Windows Store App Support
Specifies whether this project supports Windows 8.x Store apps. For more information, see /ZW (Windows Runtime Compilation), and the Windows Developer Center.