-detailedSummary[:{True or False}]
-ds[:{True or False}]
True, show detailed information at the end of the build log about the configurations that were built and how they were scheduled to nodes. -getItem:{itemName,...} Write out the value of the item or items after evaluation, without executing the build, or if either the -targets option or the -getTargetResult option is used, write out the values after the build. -getProperty:{propertyName,...} Write out the value of the property or properties after evaluation, without executing the build, or if either the -targets option or the -getTargetResult option is used, write out the values after the build. -getTargetResult:{targetName,...} Write out the output values of the specified targets. -graphBuild[:{True or False}]
-graph[:{True or False}]
-help
/? or -h
msbuild.exe -?
-ignoreProjectExtensions: {extensions}
-ignore: {extensions}
-ignoreprojectextensions:.vcproj,.sln
-inputResultsCaches[:{cacheFile; ...}]
-irc[:{cacheFile; ...}]
-isolateProjects is set to False, this sets it to True. -interactive[:{True or False}] Indicates that actions in the build are allowed to interact with the user. Don't use this argument in an automated scenario where interactivity is not expected. Specifying -interactive is the same as specifying -interactive:true. Use the parameter to override a value that comes from a response file. -isolateProjects[:{True, MessageUponIsolationViolation, False}]
-isolate[:{True, MessageUponIsolationViolation, False}]
MessageUponIsolationViolation (or its short form Message), only the results from top-level targets are serialized if the -outputResultsCache switch is supplied. This option is to mitigate the chances of an isolation-violating target on a dependency project using incorrect state due to its dependency on a cached target whose side effects wouldn't be taken into account. (For example, the definition of a property.) This mode is more restrictive, as it requires that the project graph be statically discoverable at evaluation time, but can improve scheduling and reduce memory overhead when building a large set of projects. -lowPriority[:{True or False}]
-low[:{True or False}]
-lowPriority is the same as specifying -lowPriority:True. -maxCpuCount[:{number}]
-m[:{number}]
The following example instructs MSBuild to build using three MSBuild processes, which allows three projects to build at the same time:
msbuild myproject.proj -maxcpucount:3
-noAutoResponse
-noautorsp
-nodeReuse:{value}
-nr:{value}
- True. Nodes remain after the build finishes so that subsequent builds can use them (default).
A node corresponds to a project that's executing. If you include the -maxcpucount switch, multiple nodes can execute concurrently.
-nologo Don't display the startup banner or the copyright message. -preprocess[:{filepath}]
-pp[:{filepath}]
If you specify a filepath, the aggregated project file is output to the file. Otherwise, the output appears in the console window.
For information about how to use the Import element to insert a project file into another project file, see Import element (MSBuild) and How to: Use the same target in multiple project files.
-outputResultsCache[:{cacheFile}]
-orc[:{cacheFile}]
-isolateProjects is set to False, this sets it to True. profileEvaluation:{file} Profiles MSBuild evaluation and writes the result to the specified file. If the extension of the specified file is '.md', the result is generated in Markdown format. Otherwise, a tab-separated file is produced. -property:{name}={value}
-p:{name}={value}
name is the property name and value is the property value. Specify each property separately, or use a semicolon or comma to separate multiple properties, as the following example shows:
-property:WarningLevel=2;OutDir=bin\Debug
See Common MSBuild project properties for a list of commonly used properties. The full set of available properties depends on the project type, SDK, and imported files.
-restore
-r
Restore target prior to building the actual targets. -restoreProperty:{name}={value}
-rp:{name}={value}
-property argument. name is the property name, and value is the property value. Use a semicolon or a comma to separate multiple properties, or specify each property separately. -target:{targets}
-t:{targets}
-target:PrepareResources;Compile
If you specify any targets by using this switch, they're run instead of any targets in the DefaultTargets attribute in the project file. For more information, see Target build order and How to: Specify which target to build first.
A target is a group of tasks. For more information, see Targets.
-targets[:{file}]
-ts[:{file}]
-toolsVersion:{version}
-tv:{version}
-validate:[{schema}]
-val[{schema}]
If you don't specify schema, the project is validated against the default schema.
If you specify schema, the project is validated against the schema that you specify.
The following setting is an example: -validate:MyExtendedBuildSchema.xsd
-verbosity:{level}
-v:{level}
You can specify the following verbosity levels: q[uiet], m[inimal], n[ormal] (default), d[etailed], and diag[nostic].
The following setting is an example: -verbosity:quiet
-version
-ver
@{file} Insert command-line switches from a text file. If you have multiple files, you specify them separately. For more information, see Response files. -warnAsError[:{code; ...}]
-err[:{code; ...}]
Example: -err:MSB4130
-warnNotAsError[:{code; ...}]
-noerr[:{code; ...}]
Example: -noerr:MSB4130
-warnAsMessage[:{code}; ...}]
-noWarn[:{code; ...}]
Example: -noWarn:MSB3026
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4