BuildRequestDataFlags Enumeration
Flags providing additional control over the build request.
MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0.
This enumeration has a FlagsAttribute attribute that allows a bitwise combination of its member values.
Namespace: Microsoft.Build.Execution
Assembly: Microsoft.Build (in Microsoft.Build.dll)
Syntax
'Declaration
<FlagsAttribute> _
Public Enumeration BuildRequestDataFlags
[FlagsAttribute]
public enum BuildRequestDataFlags
[FlagsAttribute]
public enum class BuildRequestDataFlags
[<FlagsAttribute>]
type BuildRequestDataFlags
public enum BuildRequestDataFlags
Members
| Member name | Description | |
|---|---|---|
| IgnoreExistingProjectState | 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. MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0.
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. |
|
| None | No flags.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. | |
| ProvideProjectStateAfterBuild | When this flag is present, BuildResult issued in response to this request will include ProjectStateAfterBuild.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. | |
| ReplaceExistingProjectInstance | When this flag is present, the existing ProjectInstance in the build will be replaced by this one.MSBuild is now included in Visual Studio instead of the .NET Framework. You can use MSBuild 12.0 side-by-side with versions previously deployed with the .NET Framework.For more information, see What's New in MSBuild 12.0. |