Reference to an assembly Relative or absolute path to the assembly (optional) Friendly display name (optional) Fusion name of the assembly (optional) Whether only the version in the fusion name should be referenced (optional, boolean) Aliases for the reference (optional) Whether the reference should be copied to the output folder (optional, boolean) Whether the types in this reference need to embedded into the target assembly - interop asemblies only (optional, boolean) The minimum required target framework version in order to use this assembly as a reference Assembly name or filename Reference to a COM component Friendly display name (optional) GUID in the form {00000000-0000-0000-0000-000000000000} Major part of the version number Minor part of the version number Locale ID Wrapper tool, such as tlbimp Is it isolated (boolean) Whether the types in this reference need to embedded into the target assembly - interop asemblies only (optional, boolean) COM component name Project Capability that may activate design-time components in an IDE. Reference to a native manifest file, or to a file that contains a native manifest Base name of manifest file Relative path to manifest file Reference full name Reference to another project Friendly display name (optional) Project GUID, in the form {00000000-0000-0000-0000-000000000000} Boolean specifying whether the outputs of the project referenced should be passed to the compiler. Default is true. Whether the exact version of the assembly should be used. Semicolon separated list of targets in the referenced projects that should be built. Default is the value of $(ProjectReferenceBuildTargets) whose default is blank, indicating the default targets. Item type to emit target outputs into. Default is blank. If the Reference metadata is set to "true" (default) then target outputs will become references for the compiler. Whether the types in this reference need to embedded into the target assembly - interop asemblies only (optional, boolean) Path to project file Source files for compiler Whether file was generated from another file (boolean) Notional path within project to display if the file is physically located outside of the project file's cone (optional) Display in user interface (optional, boolean) Semi-colon separated list of source files (wildcards are allowed) Resources to be embedded in the generated assembly Name of any file generator that is run on this item File that was created by any file generator that was run on this item Namespace into which any file generator that is run on this item should create code Notional path within project to display if the file is physically located outside of the project file's cone (optional) Display in user interface (optional, boolean) Semi-colon separated list of resource files (wildcards are allowed) Files that are not compiled, but may be embedded or published Name of any file generator that is run on this item Notional path within project to display if the file is physically located outside of the project file's cone (optional) Default, Included, Excluded, DataFile, or Prerequisite Display in user interface (optional, boolean) Copy file to output directory (optional, boolean, default false) Semi-colon separated list of content files (wildcards are allowed) XAML files that are converted to binary and compiled into the assembly Name of any file generator that is run on this item Notional path within project to display if the file is physically located outside of the project file's cone (optional) Copy file to output directory (optional, boolean, default false) Semi-colon separated list of XAML files (wildcards are allowed) File that is compiled into the assembly Name of any file generator that is run on this item Notional path within project to display if the file is physically located outside of the project file's cone (optional) Copy file to output directory (optional, boolean, default false) Semi-colon separated list of files (wildcards are allowed) XAML file that contains the application definition, only one can be defined Name of any file generator that is run on this item Notional path within project to display if the file is physically located outside of the project file's cone (optional) Copy file to output directory (optional, boolean, default false) Files that should have no role in the build process Name of any file generator that is run on this item Notional path within project to display if the file is physically located outside of the project file's cone (optional) Display in user interface (optional, boolean) The base application manifest for the build. Contains ClickOnce security information. Folder on disk Assemblies whose namespaces should be imported by the Visual Basic compiler Name of Web References folder to display in user interface Represents a reference to a web service URL to web service Display in user interface (optional, boolean) Display in user interface (optional, boolean) Display in user interface (optional, boolean) (boolean) (boolean) Default, Included, Excluded, DataFile, ManifestEntryPoint, or Prerequisite String resources to be indexed in APPX package's resource index Notional path within project to display if the file is physically located outside of the project file's cone (optional) Display in user interface (optional, boolean) Semi-colon separated list of resource files (wildcards are allowed) Name of any file which is present on the machine and should not be part of the APPX payload Reserved file name which cannot appear in the APPX package XPath queries used to extract file names from the APPX manifest APPX manifest template Notional path within project to display if the file is physically located outside of the project's folder (optional) Display in user interface (optional, boolean) A file containing APPX store association data Notional path within project to display if the file is physically located outside of the project's folder (optional) Display in user interface (optional, boolean) integer Matches the expression "\d\.\d\.\d\.(\d|\*)" Name of folder for Application Designer Name of output assembly boolean HomeSite, Relative, or Absolute boolean boolean Whether to emit symbols (boolean) none, pdbonly, or full Whether DEBUG is defined (boolean) Whether TRACE is defined (boolean) boolean Additional options to pass to the Code Analysis command line tool. Indicates whether to apply the XSL style sheet specified in $(CodeAnalysisLogFileXsl) to the Code Analysis report. This report is specified in $(CodeAnalysisLogFile). The default is false. Path to the XSL style sheet that will be applied to the Code Analysis console output. The default is an empty string (''), which causes Code Analysis to use its default console output. Culture to use for Code Analysis spelling rules, for example, 'en-US' or 'en-AU'. The default is the current user interface language for Windows. Additional reference assembly paths to pass to the Code Analysis command line tool. A fully qualified path to a directory containing reference assemblies to be used by Code Analysis. Code Analysis custom dictionaries. Semicolon-separated list of Code Analysis custom dictionaries. Wildcards are allowed. Indicates whether Code Analysis should fail if a rule or rule set is missing. The default is false. Indicates whether Code Analysis generates a report file, even when there are no active warnings or errors. The default is true. Indicates whether Code Analysis generates a '$(CodeAnalysisInputAssembly).lastcodeanalysissucceeded' file in the output folder when no build-breaking errors occur. The default is true. Indicates whether Code Analysis will ignore the default rule directories when searching for rules. The default is false. Indicates whether Code Analysis will ignore the default rule set directories when searching for rule sets. The default is false. Indicates whether Code Analysis should silently fail when analyzing invalid assemblies, such as those without managed code. The default is true. Indicates whether Code Analysis should fail silently when it analyzes invalid assemblies, such as those without managed code. The default is true. Code Analysis projects (*.fxcop) or reports to import. Semicolon-separated list of Code Analysis projects (*.fxcop) or reports to import. Wildcards are allowed. Path to the assembly to be analyzed by Code Analysis. The default is '$(OutDir)$(TargetName)$(TargetExt)'. Path to the output file for the Code Analysis report. The default is '$(CodeAnalysisInputAssembly).CodeAnalysisLog.xml'. Path to the XSL style sheet to reference in the Code Analysis output report. This report is specified in $(CodeAnalysisLogFile). The default is an empty string (''). Name of the file, without the path, where Code Analysis project-level suppressions are stored. The default is 'GlobalSuppressions$(DefaultLanguageSourceExtension)'. Indicates whether to run all overridable Code Analysis rules against all targets. This will cause specific rules, such as those within the Design and Naming categories, to run against both public and internal APIs, instead of only public APIs. The default is false. Indicates whether to output Code Analysis warnings and errors to the console. The default is false. Indicates whether to output verbose Code Analysis diagnostic info to the console. The default is false. Path to the Code Analysis installation folder. The default is '$(VSINSTALLDIR)\Team Tools\Static Analysis Tools\FxCop'. Path to the .NET Framework folder that contains platform assemblies, such as mscorlib.dll and System.dll. The default is an empty string (''). Path to the Code Analysis project (*.fxcop) to load. The default is an empty string (''). Indicates whether to suppress all Code Analysis console output other than errors and warnings. This applies when $(CodeAnalysisOutputToConsole) is true. The default is false. Semicolon-separated list of paths either to Code Analysis rule assemblies or to folders that contain Code Analysis rule assemblies. The paths are in the form '[+|-][!][file|folder]', where '+' enables all rules in rule assembly, '-' disables all rules in rule assembly, and '!' causes all rules in rule assembly to be treated as errors. For example '+D:\Projects\Rules\NamingRules.dll;+!D:\Projects\Rules\SecurityRules.dll'. The default is '$(CodeAnalysisPath)\Rules'. Semicolon-separated list of directories in which to search for rules when resolving a rule set. The default is '$(CodeAnalysisPath)\Rules' unless the CodeAnalysisIgnoreBuiltInRules property is set to true. Semicolon-separated list of Code Analysis rules. The rules are in the form '[+|-][!]Category#CheckId', where '+' enables the rule, '-' disables the rule, and '!' causes the rule to be treated as an error. For example, '-Microsoft.Naming#CA1700;+!Microsoft.Naming#CA1701'. The default is an empty string ('') which enables all rules. A .ruleset file which contains a list of rules to run during analysis. The string can be a full path, a path relative to the project file, or a file name. If a file name is specified, the CodeAnalysisRuleSetDirectories property will be searched to find the file. The default is an empty string (''). Semicolon-separated list of directories in which to search for rule sets. The default is '$(VSINSTALLDIR)\Team Tools\Static Analysis Tools\Rule Sets' unless the CodeAnalysisIgnoreBuiltInRuleSets property is set to true. Comma-separated list of the type ('Active', 'Excluded', or 'Absent') of warnings and errors to save to the output report file. The default is 'Active'. Indicates whether Code Analysis should search the Global Assembly Cache (GAC) for missing references that are encountered during analysis. The default is true. Indicates whether to output a Code Analysis summary to the console after analysis. The default is false. The time, in seconds, that Code Analysis should wait for analysis of a single item to complete before it aborts analysis. Specify 0 to cause Code Analysis to wait indefinitely. The default is 120. Indicates whether to treat all Code Analysis warnings as errors. The default is false. Indicates whether to update the Code Analysis project (*.fxcop) specified in $(CodeAnalysisProject). This applies when there are changes during analysis. The default is false. Indicates whether to include the name of the rule when Code Analysis emits a suppression. The default is true. Whether Visual Studio should do its own faster up-to-date check before Building, rather than invoke MSBuild to do a possibly more accurate one. You would set this to false if you have a heavily customized build process and builds in Visual Studio are not occurring when they should. Sets the /sdkpath switch for a VB project to the specified value Web, Unc, or Disk boolean Matches the expression "\d\.\d\.\d\.\d" Whether standard libraries (such as mscorlib) should be referenced automatically (boolean) Comma separated list of disabled warnings boolean Should compiler optimize output (boolean) Option Compare setting (Text or Binary) Should Option Explicit be set (On or Off) Should Option Strict be set (On or Off) Should Option Infer be set (On or Off) Path to output folder, with trailing slash Type of output to generate (WinExe, Exe, or Library) Command line to be run at the end of build Command line to be run at the start of build Semi-colon separated list of folders to search during reference resolution Indicates whether to run Code Analysis during the build. Type that contains the main entry point boolean boolean Hours, Days, or Weeks Foreground or Background boolean boolean integer between 0 and 4 inclusive Comma separated list of warning numbers to treat as errors Use hard links if possible when copying files during creation of APPX packages Skip unchanged files when copying files during creation of APPX packages Generate resource index files (PRI) during packaging Enable signing of APPX packages Generate symbol package when an APPX package is created Create test layout when an APPX package is created Enable validation of APPX packages Enable harvesting of WinMD registration information Enable prepending initial path when indexing RESW and RESJSON files in class libraries Initial path when indexing RESW and RESJSON files in class libraries Enable auto increment of an APPX package revision Location where APPX packages will be saved Additional qualifier to append to AppxPackageDir Full path to the APPX manifest schema file File name of the final APPX manifest Full path to makepri.exe utility File name to use for project-specific resource index (PRI) File name of the final resource index (PRI) Full path to final resource index (PRI) file File name of the APPX package recipe File name of the final APPX package recipe Name of the folder used to prepare the APPX package layout Full path of the folder used to prepare the APPX package layout Default hash in URI form, used for signing APPX package when app store Mark current project as capable of being packaged as an APPX package Name of the binary containing managed WinMD in-proc implementation Enable incremental registration of the APPX layout Include primary build outputs into the APPX package payload Include debug symbols into the APPX package payload Include documentation into the APPX package payload Include satellite DLLs into the APPX package payload Include source files into the APPX package payload Include content files into the APPX package payload Include SGen files into the APPX package payload Include files marked as 'Copy local' into the APPX package payload Include COM files into the APPX package payload Include custom output group into the APPX package payload Include WinMD artifacts into the APPX package payload Include SDK redist into the APPX package payload Include resource index (PRI) files into the APPX package payload Include resolved SDK references into the APPX package payload Name of the APPX package to generate Name of the APPX store container to generate Name of the folder where test APPX packages will be copied Full path to the APPX package file Full path to the APPX symbol package file Additional parameters to pass to makepri.exe when generating project PRI file Additional parameters to pass to makepri.exe when generating PRI file for a portable library Additional parameters to pass to makepri.exe when merging PRI files Additional parameters to pass to makepri.exe when extracting payload file names