Set up automated builds for your UWP app
You can use Visual Studio Team Services (VSTS) to create automated builds for UWP projects. In this article, we’ll look at different ways to do that. We’ll also show you how to perform these tasks by using the command line so that you can integrate with other build systems such as AppVeyor.
Select the right type of build agent
Choose the type of build agent that you want VSTS to use when it executes the build process. A hosted build agent is deployed with the most common tools and sdks, and it will work for most scenarios, see the Software on the hosted build server article. However, you can create a custom build agent if you need more control over the build steps. You can use the following table to help you make that decision.
|Scenario||Custom Agent||Hosted Build Agent|
|Basic UWP build (including .NET native)||✅||✅|
|Generate packages for Sideloading||✅||✅|
|Generate packages for Store submission||✅||✅|
|Use custom certificates||✅|
|Build targeting a custom Windows SDK||✅|
|Run unit tests||✅|
|Use incremental builds||✅|
Create a custom build agent (optional)
If you choose to create a custom build agent, you’ll need the Universal Windows Platform tools. These tools are part of Visual Studio. You can use the community edition of Visual Studio.
To learn more, see Deploy an agent on Windows.
To run UWP unit tests, you’ll have to do these things:
- Deploy and start your app
- Run the VSTS agent in interactive mode
- Configure your agent to auto-logon after a reboot
Set up an automated build
We’ll start with the default UWP build definition that’s available in VSTS and then show you how to configure that definition so that you can accomplish more advanced build tasks.
Add the certificate of your project to a source code repository
VSTS works with both TFS and GIT based code repositories.
If you use a Git repository, add the certificate file of your project to the repository so that the build agent can sign the app package. If you don’t do this, the Git repository will ignore the certificate file. To add the certificate file to your repository, right-click the certificate file in Solution Explorer, and then in the shortcut menu, choose the Add Ignored File to Source Control command.
We’ll discuss advanced certificate management later in this guide.
To create your first build definition in VSTS, navigate to the Builds tab, and then select the + button.
In the list of build definition templates, choose the Universal Windows Platform template.
This build definition contains the following build tasks:
- NuGet restore ***.sln
- Build solution ***.sln
- Publish Symbols
- Publish Artifact: drop
Configure the NuGet restore build task
This task restores the NuGet Packages that are defined in your project. Some packages require a custom version of NuGet.exe. If you’re using a package that requires one, refer to that version NuGet.exe in your repo and then reference it in the Path to NuGet.exe advanced property.
Configure the Build solution build task
This task compiles any solution that’s in the working folder to binaries and produces the output app package file. This task uses MSbuild arguments. You’ll have to specify the value of those arguments. Use the following table as a guide.
|AppxPackageDir||$(Build.ArtifactStagingDirectory)\AppxPackages||Defines the folder to store the generated artifacts.|
|AppxBundlePlatforms||$(Build.BuildPlatform)||Allows you to define the platforms to include in the bundle.|
|AppxBundle||Always||Creates an appxbundle with the appx files for the platform specified.|
|UapAppxPackageBuildMode||StoreUpload||Defines the kind of app package to generate. (Not included by default)|
If you want to build your solution by using the command line, or by using any other build system, run msbuild with these arguments.
/p:AppxPackageDir="$(Build.ArtifactStagingDirectory)\AppxPackages\\" /p:UapAppxPackageBuildMode=StoreUpload /p:AppxBundlePlatforms="$(Build.BuildPlatform)" /p:AppxBundle=Always
The parameters defined with the $() syntax are variables defined in the build definition, and will change in other build systems.
To view all predefined variables, see Use build variables.
Configure the Publish Artifact build task
This task stores the generated artifacts in VSTS. You can see them in the Artifacts tab of the build results page.
VSTS uses the
$(Build.ArtifactStagingDirectory)\AppxPackages folder that we previously defined.
Because we’ve set the
UapAppxPackageBuildMode property to
StoreUpload, the artifacts folder includes the package that recommended for submission to the Store (.appxupload). Note that you can also submit a regular app pacakge (.appx/.msix) or an app bundle (.appxbundle/.msixbundle) to the Store. For the purposes of this article, we'll use the .appxupload file.
By default, the VSTS agent maintains the latest generated app packages. If you want to store only the artifacts of the current build, configure the build to clean the binaries directory. To do that, add a variable named
Build.Clean and then set it to the value
all. To learn more, see Specify the repository.
The types of automated builds
Next, you’ll use your build definition to create an automated build. The following table describes each type of automated build that you can create.
|Type of Build||Artifact||Recommended Frequency||Description|
|Continuous Integration||Build Log, Test Results||Each commit||This type of build is fast and run several times a day.|
|Continuous Deployment build for sideloading||Deployment Packages||Daily||This type of build can Include unit tests but it takes a bit longer. It allows manual testing and you can integrate it with other tools such as HockeyApp.|
|Continuous Deployment build that submits a package to the Store||Publishing Packages||On demand||This type of build creates a package that you can publish to the Store.|
Let’s look at how to configure each one.
Set up a Continuous Integration (CI) build
This type of a build helps you to diagnose code related problems quickly. They’re typically executed for only one platform, and they don’t need to be processed by the .NET native toolchain. Also, with CI builds, you can run unit tests that produce a test results report.
If you want to run UWP unit tests as part of your CI build you’ll need to use a custom build agent instead of the hosted build agent.
If you bundle more than one app in the same solution, you might receive an error. See the following topic for help resolving that error: Address errors that appear when you bundle more than one app in the same solution.
Configure a CI build definition
Use the default UWP template to create a build definition. Then, configure the Trigger to execute on each check in.
Because the CI build won’t be deployed to users, it’s a good idea to maintain different versioning numbers to avoid confusion with the CD builds. For example:
Configure a custom build agent for unit testing
- Enable Developer Mode on your PC. See Enable your device for development for more information.
- Enable the service to run as an interactive process. To learn more, see Deploy an agent on Windows.
- Deploy the signing certificate to the agent.
To deploy a signing certificate, double-click the
.cer file, choose Local Machine, and then choose Trusted People Store.
Configure the build definition to run UWP Unit Tests
To execute a unit test, use the Visual Studio Test build step.
UWP unit tests are executed in the context of a given appxrecipe file so you can’t use the generated bundle. Also, you’ll have to specify the path to a concrete platform appxrecipe file. For example:
In order for the tests to run a console parameter will have to be added to vstest.console.exe. This parameter can be provide through: Execution Options => Other console options. Please add following parameter:
Use the following command to execute the unit tests locally from the command line:
"%ProgramFiles(x86)%\Microsoft Visual Studio 14.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow\vstest.console.exe"
Access test results
In VSTS, the build summary page shows the test results for each build that executes unit tests. From there, you can open the Test Results page to see more detail about the test results.
Improve the speed of a CI build
If you want to use your CI build only to monitor the quality of your check-ins, you can reduce your build times.
To improve the speed of a CI build
- Build for only one platform.
- Edit the BuildPlatform variable to use only x86.
- In the build step, add /p:AppxBundle=Never to the MSBuild Arguments property, and then set the Platform property.
- In the unit test project, disable .NET Native.
To do that, open the project file, and in the project properties, set the
UseDotNetNativeToolchain property to
Using the .NET native tool chain is an important part of the workflow and should still be used to test release builds.
Address errors that appear when you bundle more than one app in the same solution
If you add more than one UWP project to your solution, and then try to create a bundle, you might receive an error like this one:
MakeAppx(0,0): Error : Error info: error 80080204: The package with file name "AppOne.UnitTests_0.1.2595.0_x86.appx" and package full name "8ef641d1-4557-4e33-957f-6895b122f1e6_0.1.2595.0_x86__scrj5wvaadcy6" is not valid in the bundle because it has a different package family name than other packages in the bundle
This error appears because at the solution level, it’s not clear which app should appear in the bundle.
To resolve this issue, open each project file and add the following properties at the end of the first
Then, remove the
AppxBundle msbuild argument from the build step.
Set up a continuous deployment build for sideloading
When this type of build completes, users can download the app bundle file from the artifacts section of the build results page. If you want to beta test the app by creating a more complete distribution, you can use the HockeyApp service. This service offers advanced capabilities for beta testing, user analytics and crash diagnostics.
Applying version numbers to your builds
The manifest file contains the app version number. Update the manifest file in your source control repository to change the version number. Another way to update the version number of your app is to use the build number that is generated by VSTS, and then modify the app manifest just before you compile the app. Just don’t commit those changes to the source code repository.
You’ll have to define your versioning build number format in the build definition, and then use the resulting version number to update the AppxManifest and optionally, the AssemblyInfo.cs files, before you compile.
Define the build number format in the General tab of your build definition.
For example, if you set the build number format to the following value:
VSTS generates a version number like:
The Store will require that the last number in the version to be 0.
So that you can extract the version number and apply it to the manifest and/or
AssemblyInfo files, use a custom PowerShell script (available here). That script reads the version number from the environment variable
BUILD_BUILDNUMBER, and then modifies the AssemblyInfo and AppxManifest files. Make sure to add this script to your source repository, and then configure a PowerShell build task as shown here:
$(AppxVersion) variable contains the version number. You can use that number in other build steps.
Optional: Integrate with HockeyApp
First, install the HockeyApp Visual Studio extension. You will need to install this extension as a VSTS administrator.
Next, configure the HockeyApp connection by using this guide: How to use HockeyApp with Visual Studio Team Services (VSTS) or Team Foundation Server (TFS). You can use your Microsoft account, social media account or just an email address to set up your HockeyApp account. The free plan comes with two apps, one owner, and no data restrictions.
Then, you can create a HockeyApp app manually, or by uploading an existing app package file. To learn more, see How to create a new app.
To use an existing app package file, add a build step, and set the Binary File Path parameter of the build step.
To set this parameter, combine the app name, the AppxVersion variable and the supported platforms together into one string such as this one:
Although the HockeyApp task allows you to specify the path to the symbols file, it’s a best practice to include the symbols with the bundle.
Set up a continuous deployment build that submits a package to the Store
To generate Store submission packages, associate your app with the Store by using the Store Association Wizard in Visual Studio.
The Store Association Wizard generates a file named Package.StoreAssociation.xml that contains the Store association information. If you store your source code in a public repository such as GitHub, this file will contain all the app reserved names for that account. You can exclude or delete this file before making it public.
If you don’t have access to the Dev Center account that was used to publish the app, you can follow the instructions in this document: Building an app for a 3rd party? How to package their Store app.
Then you need to verify that the build step includes the following parameter:
This will generate an upload file that can be submitted to the Store.
Configure automatic Store submission
Use the Visual Studio Team Services extension for the Microsoft Store to integrate with the Store API, and send your app package to the Store.
You need to connect your Dev Center account with Azure Active Directory (AD), and then create an app in your AD to authenticate the requests. You can follow the guidance in the extension page to accomplish that.
Once you’ve configured the extension, you can add the build task, and configure it with your app ID and the location of the upload file.
Where the value of the
Package File parameter will be:
You have to manually activate this build. You can use it to update existing apps but you can’t use it to for your first submission to the Store. For more information, see Create and manage Store submissions by using Microsoft Store Services.
Best Practices for Sideloading apps
If you want to distribute your app without publishing it to the Store, you can sideload your app directly to devices as long as those devices trust the certificate that was used to sign the app package.
Add-AppDevPackage.ps1 PowerShell script to install apps. This script will add the certificate to the Trusted Root Certification section for the local machine, and will then install or update the app package file.
Sideloading your app with the Windows 10 Anniversary Update
In the Windows 10 Anniversary Update, you can double-click the app package file and install your app by choosing the Install button in a dialog box.
This method doesn’t install the certificate or the associated dependencies.
If you want to distribute your Windows app packages from a website such as VSTS or HockeyApp, you’ll need to add that site to the list of trusted sites in your browser. Otherwise, Windows marks the file as locked.
Best Practices for Signing Certificates
Visual Studio generates a certificate for each project. This makes it difficult to maintain a curated list of valid certificates. If you plan to create several apps, you can create a single certificate to sign all of your apps. Then, each device that trusts your certificate will be able to sideload any of your apps without installing another certificate. To learn more, see Create a certificate for package signing.
Create a Signing Certificate
Use the MakeCert.exe tool to create a certificate.
The following example creates a certificate by using the MakeCert.exe tool.
MakeCert /n publisherName /r /h 0 /eku "18.104.22.168.22.214.171.124.3,126.96.36.199.4.1.3188.8.131.52" /e expirationDate /sv MyKey.pvk MyKey.cer
Then you can use Pvk2Pfx tool to generate a PFX file that contains the private key protected with a password.
Provide these certificates to each machine role:
|Developer/Build Machine||Sign Builds||MyCert.PFX||Current User/Personal|
|Developer/Build Machine||Run||MyCert.cer||Local Machine/Trusted People|
|User||Run||MyCert.cer||Local Machine/Trusted People|
Note: You can also use an enterprise certificate that is already trusted by your users.
Sign your UWP app
Visual Studio and MSBuild offers different options to manage the certificate that you use to sign the app:
One option is to include the certificate with the private key (normally in the form of a .PFX file) in your solution, and then reference the pfx in the project file. You can manage this by using the Package tab of the manifest editor.
Another option is to install the certificate onto the build machine (Current User/Personal), and then use the Pick from Certificate store option. This specifies the Thumbprint of the certificate in the project file so that the certificate should be installed in all the machines that will be used to build the project.
Trust the signing certificate in the target devices
A target device has to trust the certificate before the app can be installed on it.
Register the public key of the certificate in the Trusted People or Trust Root location in the Local Machine certificate store.
The quickest way to register the certificate is to double-click in the .cer file, and then follow the steps in the wizard to save the certificate in the Local Machine and Trusted People store.