Share via


CheckInOptions2 Enumeration

This enumeration has a FlagsAttribute attribute that allows a bitwise combination of its member values.

Namespace:  Microsoft.TeamFoundation.VersionControl.Common
Assembly:  Microsoft.TeamFoundation.VersionControl.Common (in Microsoft.TeamFoundation.VersionControl.Common.dll)

Syntax

'Declaration
<FlagsAttribute> _
Public Enumeration CheckInOptions2
[FlagsAttribute]
public enum CheckInOptions2
[FlagsAttribute]
public enum class CheckInOptions2
[<FlagsAttribute>]
type CheckInOptions2
public enum CheckInOptions2

Members

Member name Description
AllContentUploaded The server will permit a call to CheckIn with a null or empty list of items to check in, (checkin /all) even if there is a change with the edit bit set.
AllowUnchangedContent t=The server will allow items which have a pending edit to be checked in even if the content hasn't changed instead of undoing the change (default)
DeleteShelveset Delete the shelveset after a successful submission into the repository
NoAutoResolve Used only on the client. Instructs the client not to try to auto resolve conflicts
NoConflictsCheckForGatedCheckIn This flag only affects the server's behavior when the server paths being checked in affect a gated build definition. In this case the server will ordinarily call CheckPendingChanges before shelving the workspace and throwing back a GatedCheckinException. If the call to CheckPendingChanges creates conflicts, then no GatedCheckinException will be thrown; instead CheckIn fails and informs the user that they must resolve their conflicts. If this flag is specified, this call to CheckPendingChanges is skipped. This allows the gated checkin shelveset to be created even when the items being checked in are not at latest, for example. The build agent workspace will unshelve the shelveset and attempt to resolve conflicts at that time.
None
OverrideGatedCheckIn Bypass gated checkin validation for this checkin
QueueBuildForGatedCheckIn Automatically queue the build for gated checkin validation if it is possible
SuppressEvent Suppress events for this checkin
ValidateCheckInOwner Make sure that the identity specified as the checkin owner refers to a valid user

See Also

Reference

Microsoft.TeamFoundation.VersionControl.Common Namespace