Flags providing additional control over the build request.
This enumeration has a FlagsAttribute attribute that allows a bitwise combination of its member values.
Assembly: Microsoft.Build (in Microsoft.Build.dll)
|When this flag is present and the project has previously been built on a node whose affinity is incompatible with the affinity this request requires, this build request ignores the project state (but not the target results) that was previously generated. |
This behavior, when this flag is present, is not usually desired. This flag is provided only for those cases where the client knows that the new build request does not depend on the project state generated by a previous request. Setting this flag can provide a performance boost in the case of incompatible node affinities, because MSBuild would otherwise have to serialize the project state from one node to another, Serializing the project state can be expensive, depending on the amount of data the project has previously generated.
This flag has no effect on target results, so if a previous request has built a target, the new request will not re-build the target. Additionally, none of the project state mutations which occurred as a consequence of previously building that target will be re-applied.
|When this flag is present, BuildResult issued in response to this request will include ProjectStateAfterBuild.|
|When this flag is present, the existing ProjectInstance in the build will be replaced by this one.|
Windows 8.1, Windows Server 2012 R2, Windows 8, Windows Server 2012, Windows 7, Windows Vista SP2, Windows Server 2008 (Server Core Role not supported), Windows Server 2008 R2 (Server Core Role supported with SP1 or later; Itanium not supported)
The .NET Framework does not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.