InformationNodeConverters.AddBuildStep Method (IBuildDetail, String, String, DateTime, BuildStepStatus)

Adds a top-level build step to the specified build. Saves to the server.

Namespace:  Microsoft.TeamFoundation.Build.Client
Assembly:  Microsoft.TeamFoundation.Build.Client (in Microsoft.TeamFoundation.Build.Client.dll)

Syntax

'Declaration
Public Shared Function AddBuildStep ( _
    build As IBuildDetail, _
    name As String, _
    message As String, _
    time As DateTime, _
    status As BuildStepStatus _
) As IBuildStep

public static IBuildStep AddBuildStep(
    IBuildDetail build,
    string name,
    string message,
    DateTime time,
    BuildStepStatus status
)

public:
static IBuildStep^ AddBuildStep(
    IBuildDetail^ build, 
    String^ name, 
    String^ message, 
    DateTime time, 
    BuildStepStatus status
)

static member AddBuildStep : 
        build:IBuildDetail * 
        name:string * 
        message:string * 
        time:DateTime * 
        status:BuildStepStatus -> IBuildStep

public static function AddBuildStep(
    build : IBuildDetail, 
    name : String, 
    message : String, 
    time : DateTime, 
    status : BuildStepStatus
) : IBuildStep

Parameters

• build
  Type: Microsoft.TeamFoundation.Build.Client.IBuildDetail

  The build to which the build step will be added.

• name
  Type: System.String

  The name of the build step to be added.

• message
  Type: System.String

  The message of the build step to be added.

• time
  Type: System.DateTime

  The start and finish time of the build step to be added.

• status
  Type: Microsoft.TeamFoundation.Build.Client.BuildStepStatus

  The status of the build step to be added.

Return Value

Type: Microsoft.TeamFoundation.Build.Client.IBuildStep
The added build step instance.

Remarks

Note that build steps are no longer used after Visual Studio Application Lifecycle Management 2008 Team Foundation Server and have been replaced with various new information node types, including IBuildMessage, IBuildError, IBuildWarning, and IActivityTracking. Therefore, when you add information nodes to builds which will be primarily viewed from newer clients (for example, Team Foundation Server 2010), these new types are better than IBuildSteps.

.NET Framework Security

• Full trust for the immediate caller. This member cannot be used by partially trusted code. For more information, see Using Libraries from Partially Trusted Code.

See Also

Reference

InformationNodeConverters Class

AddBuildStep Overload

Microsoft.TeamFoundation.Build.Client Namespace