Provides access to various Windows SDK tools.

  • About
  • Details
  • Release Notes
  • Installation

Enterprise Windows Features and flexible ARA

Using the Windows SDK as a pre-packaging tool to create a release package from within BuildMaster allows you to easily add built-in operation to any deployment plan.


Built-In Operations include:

  • Build MSBuild Project –Builds a project or solution using MSBuild.
  • Sign Binary –Signs .exe or .dll files using an installed code signing certificate.
  • Write Assembly Versions –Updates AssemblyVersion, AssemblyFileVersion, and AssemblyInformationalVersion  Attributes (in AssemblyInfo source files).
  • XDT Transform –Performs an XDT transform on a configuration file.

Using The MSBuild Operation of this extension

Below, shows how to create a release package within BuildMaster using an outside repository. In this case, we’ll be using GitHub as our repository for an application called Accounts.

If you’d like to follow along step-by-step, you can fork the Accounts Repository into your own account.

Step 1: Install and Configure Extensions

Click Administration > Click BuildMaster Extensions > Click GitHub > Click Install This Extension

Click Administration > Click BuildMaster Extensions > Click NuGet > Click Install This Extension

After the extensions are installed, BuildMaster will automatically restart, and both GitHub and NuGet will now be in the Up-to-Date Extensions.

Click Administration > Click Resource Credentials > Click Create Credential > Click GitHub

We’ll create a GitHub resource credential by filling out appropriate fields like User name, Repository, and Password . NuGet requires no additional configuration.

Step 2: Create Application

Click Applications > Click Create Application > Set Name to Accounts > Click Create

When creating the application, the Integration, Testing, and Production environments will be added by default as the initial pipeline.

Step 3: Edit Deployment Plan

Click Plans > Click Deploy Accounts

BuildMaster has automatically created a simple deployment plan by default. The plan doesn't do much, but we can edit it so that it will deploy the artifact that we'll import through the pipeline.

Edit the General Block, and set a server for the plan to be run on. Note that you can also target environments and servers to execute operations on from the pipeline stage, but for this tutorial, we'll just set it here.

Next, drag a Deploy Artifact operation into the edited General Block. Set the Artifact name to "Websites", and the Target directory to C:\Websites\$EnvironmentName\Accounts. Using $EnvironmentName will create a new folder for each environment that the application is deployed to, and demonstrates one way to generalize a deployment plan for use in multiple environments.

After saving the Deploy Artifact Operation save the plan.

This plan will only deploy an Artifact. First we must create the artifact (Websites) which we will do in BuildMaster. So, we need to create a new plan called Build Accounts.

Step 4: Create a New Build Plan

Crate a plan by clicking the Create Plan button and name the plan Build Accounts

First, add a General Block with a short description, like "Build Accounts Website."

Next, we’ll add a Get Source operation that will pull the latest files from a repository (in this case, GitHub) and store them in a temporary workspace called $WorkingDirectory. We'll use the GitHub resource credential we've already created.

Now, we’ll add a Write Assembly Versions operation which will increase the build number by 1 each time by default.

Since this build requires NuGet packages, the next step is to drag an Install NuGet Packages operation with default settings.

Now we are prepared to build our Accounts web application simply by adding a Build MSBuild Project operation with the appropriate solutions and configurations.

To turn this build into an Artifact, add a Create Artifact operation. Name the artifact "Websites" because that is the artifact that we used in the deployment plan we first created.

You can view the plan in either visual mode or text mode.

Visual Mode

> A deployment plan(Visual Mode)

Text Mode (OtterScript)

A deployment plan (Text Mode)

Step 5: Edit Application Pipeline and Set Build Plan

When we created the application, a simple pipeline was also created which we can now edit.

Click Pipelines > Click Accounts

You can see that the three stages-Integration, Testing, and Production-are all in the pipeline and all have the Deploy Account plan assigned to them already. All we need to do is create the Artifact with our build plan; we’ll create a new Stage for that.

Click Add Stage > Set Name to Build > Set Pipeline position to 0 > Click Save Stage

We’ll add a target to the Build stage using our build plan (Build Accounts) and our local server.

Step 6: Creating a Release and Deploying

After setting the build target, we will create a Release that builds and deploys this artifact. The release number can be anything, but defaults to 0.0.0.

Click Releases > Click Create Release > Click Create Package

BuildMaster will now run the build plan we've set up and create the artifact.

We can see that there has been an artifact created called "Website."

You can now run the artifact through the rest of the pipeline simply by clicking [Deploy] in each successive stage. Of course, you can also configure gates, listeners, permissions to ensure that a proper process is followed.

You can further verify that the deployment was successful by checking the drive used when setting up the deployment plan. There will be three folders under /Website -one for Integration, Testing, and Production, all with the deployed files.



No notes for this release

Download (requires BuildMaster 5.6.0 or newer)



No notes for this release

Download (requires BuildMaster 5.1.1 or newer)


  • 40 - FIX: Invalid path to ctt.exe when executing on an agent

Download (requires BuildMaster 5.1.1 or newer)



No notes for this release

Download (requires BuildMaster 5.1.1 or newer)



No notes for this release

Download (requires BuildMaster 5.1.0 or newer)



No notes for this release

Download (requires BuildMaster 5.0.4 or newer)


  • 39 - Add Certificate Hash to ClickOnce Action if Cert Not Found

Download (requires BuildMaster 4.9.0 or newer)



No notes for this release

Download (requires BuildMaster 5.0.0 or newer)


  • 37 - SDK 4.8 Compatibility

Download (requires BuildMaster 4.8.0 or newer)


  • 35 - Source control picker in .NET Wizard recipe should display the file picker

Download (requires BuildMaster 4.5.2 or newer)


  • 34 - FIX: .NET application recipe for BuildMaster 4.5
  • 33 - FIX: MissingMethodException in Build ASP.NET application action for BuildMaster 4.5

Download (requires BuildMaster 4.5.2 or newer)


  • 32 - Improve extension configurer editor
  • 31 - Add MSBuild tools path to extension configurer

Download (requires BuildMaster 4.4.1 or newer)


  • 30 - SDK 4.4 updates for custom extension recipe

Download (requires BuildMaster 4.4.1 or newer)


  • 29 - Support for building/publishing Azure websites

Download (requires BuildMaster 4.3.3 or newer)


  • 28 - FIX: Server should be specified for actions in Create .NET Application recipe
  • 27 - FIX: Create .NET Application recipe does not work in BuildMaster 4.3

Download (requires BuildMaster 4.3.3 or newer)


  • 26 - UI refresh for actions
  • 22 - Replacing Copyright from AssemblyInfo
  • 19 - Unset read-only attribute in Write Assembly Version action if necessary
  • 17 - Add "Additional Arguments" to Execute/Build MSBuild Actions

Download (requires BuildMaster 4.2.0 or newer)


  • 23 - Extension-creating Recipe Tweaks

Download (requires BuildMaster 4.2.0 or newer)


  • 17 - Add "Additional Arguments" to Execute/Build MSBuild Actions
  • 16 - Rename "Build MSBuild Project" Action to "Build Visual Studio Project"

Download (requires BuildMaster 4.2.0 or newer)


  • 6 - Escape quotes/semicolons on MSBuild properties
  • 4 - Do not use custom logger if .NET < 4.0
  • 12 - New action to manually perform an XDT transform on configuration files
  • 11 - New Build ASP.NET Web or MVC application project action
  • 10 - Custom BuildLogger.exe is not receiving arguments correctly

Download (requires BuildMaster 4.0.7 or newer)


  • 9 - Update extension application recipe for .NET 4.0 and add application creation examples

Download (requires BuildMaster 4.0.7 or newer)


  • 8 - Change wizard step order for Create .NET recipe
  • 7 - FIX: Create .NET recipe does not work with some source control providers

Download (requires BuildMaster 4.0.7 or newer)


  • 5 - Support for VS11 Web Application targets

Download (requires BuildMaster 4.0.3 or newer)


  • 3 - Prepare ClickOnce application Certificate password not persisted by action editor

Download (requires BuildMaster 4.0.3 or newer)


  • 2 - FIX: Typo in code signing action description
  • 1 - FIX: MSBuild action hangs when the project file is not accessible

Download (requires BuildMaster 4.0.2 or newer)



No notes for this release

Download (requires BuildMaster 4.0.0 or newer)



No notes for this release

Download (requires BuildMaster 4.0.0 or newer)



No notes for this release

Download (requires BuildMaster 3.5.0 or newer)



No notes for this release

Download (requires BuildMaster 3.0.0 or newer)

If your installation of BuildMaster can access, simply navigate to Admin > Extensions, and install or update extensions from the gallery.

You can also manually install the extension.

  1. Copy the extension file (WindowsSDK.bmx) to the Extension Library path (by default, this is c:\BuildMaster\Extensions).
  2. Restart the BuildMaster Service (Admin > Service).
  3. Restart the BuildMaster Web Application (Admin > All Settings > Save).
  4. Verify that the new extension has been loaded (Admin > Extensions)