InformationNodeConverters.AddBuildStep Method (IBuildDetail, String, String, DateTime)
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, _
startTime As DateTime _
) As IBuildStep
public static IBuildStep AddBuildStep(
IBuildDetail build,
string name,
string message,
DateTime startTime
)
public:
static IBuildStep^ AddBuildStep(
IBuildDetail^ build,
String^ name,
String^ message,
DateTime startTime
)
static member AddBuildStep :
build:IBuildDetail *
name:string *
message:string *
startTime:DateTime -> IBuildStep
public static function AddBuildStep(
build : IBuildDetail,
name : String,
message : String,
startTime : DateTime
) : IBuildStep
Parameters
build
Type: Microsoft.TeamFoundation.Build.Client.IBuildDetailThe build to which the build step will be added.
name
Type: System.StringThe name of the build step to be added.
message
Type: System.StringThe message of the build step to be added.
startTime
Type: System.DateTimeThe start time 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.