Skip to content
Windows Template Studio quickly builds a UWP app, using a wizard-based UI to turn your needs into a foundation of Windows 10 patterns and best practices.
Rich Text Format C# Visual Basic PowerShell Batchfile HTML
Branch: dev
Clone or download
Latest commit ea1ec39 Oct 9, 2019

Windows Template Studio

Windows Template Studio (WinTS) is a Visual Studio 2017 and 2019 Extension that accelerates the creation of new Universal Windows Platform (UWP) apps using a wizard-based experience. The resulting UWP project is well-formed, readable code that incorporates the latest Windows 10 features while implementing proven patterns and best practices. Sprinkled throughout the generated code we have links Docs, Stack Overflow and blogs to provide useful insights. WinTS supports creating apps in C# or VB.Net.

Windows Template Studio screenshot

Build Status

Branch CI Test Version Version
master Build status Prerelease Version Production Version
dev Build status Nightly Version
Branch Full Tests OneByOne Tests WACK Tests
master Full Integration Tests OneByOne Integration Tests Wack Tests
dev Full Integration Tests OneByOne Integration Tests Wack Tests

The builds include test verifications to validate the contributions:

  • CI Build: Includes all unit test + minimum integration verifications (minimum generation + build + code style rules). Runs every PR requested / PR accepted.
  • Full Tests: Includes tests to verify combinations and variations of templates from a project generation point of view and builds the solutions generated to ensure no build time issues found. Runs every PR accepted and takes longer to be completed.
  • One By One Tests: Includes tests to verify every template individually from a project generation point of view and builds the solutions generated to ensure no build time issues found. Runs every PR accepted and takes longer to be completed.
  • Wack Tests: Includes tests that run the App Certification Kit against the generated projects to ensure there are no issues blocking a submission to the store. Runs once nightly and takes quite a while to complete.


Windows Template Studio approaches UWP app creation using the following six attribute sets:

  • Project type: First, how do you want your app's UI navigation to behave? We support four project types: basic, navigation pane, pivot and tabs, and a menu bar.
  • App design pattern: Next, what coding pattern do you want to use in your project, we currently support five common patterns: code behind, basic MVVM, MVVMLight, Caliburn.Micro, and Prism.
  • App pages: To accelerate app creation, we provide a number of app page templates you can use to add common UI pages into your new app. We currently include everything from a blank page, to common layouts (e.g., master/detail, tabbed, web view), to pages that implement common patterns (e.g., app settings, map control). Use the wizard to add as many of each page as you need, providing a name for each one, and we'll generate them for you.
  • Windows 10 features: Specify which UWP capabilities you want to use in your app, and we'll build out the framework for the features into your app, tagging TODO items. Currently supported features cover analytics, application launching, application lifecycle (settings storage, suspend and resume, multiple views), background work, connected experiences (share source and target), and user interaction (app notifications, Live tiles, prompts, feedback, drag & drop and theme selection).
  • Services: Connect to data services, setup identity logins for your application, and enforce rules with the XAML Styler extension.
  • Automated Tests: Lastly, you can include test projects for your application to run unit tests or use Selenium-like UI test automation.

After selecting the items wanted in your UWP app, you can extend the generated code.


Known issues

  • You can't have side-by-side versions (nightly/pre-release/release) of Windows Template Studio VSPackage into a single instance of Visual Studio.

Feedback, Requests and Roadmap

Please use GitHub issues for feedback, questions or comments.

If you have specific feature requests or would like to vote on what others are recommending, please go to the GitHub issues section as well. We would love to see what you are thinking.

Here is what we're currently thinking in our roadmap.


Do you want to contribute? We would love to have you help out. Here are our contribution guidelines.


  1. Generated templates will be kept simple.
  2. Generated templates are a starting point, not a completed application.
  3. Generated templates must be able to compile and run once generated.
  4. Generated templates should work on all device families.
  5. Templates should have comments to aid developers. This includes links to signup pages for keys, MSDN, blogs and how-to's. All guidance provide should be validated from either the framework/SDK/library’s creator.
  6. All features will be supported for two most recent RTM Windows 10 Updates. Those supported releases are Windows 10 October 2018 Update (version 1809) and Windows 10 April 2018 Update (version 1803).
  7. Templates released in production will try to adhere to the design language used in the current release of Windows 10.
  8. Code should follow .NET Core coding style.

This project has adopted the code of conduct defined by the Contributor Covenant to clarify expected behavior in our community. For more information see the .NET Foundation Code of Conduct.


This code is distributed under the terms and conditions of the MIT license.

Privacy Statement

The extension logs basic telemetry regading what is selected in the wizard. Our Telemetry Data page has the trends from the telemetry. Please read the Microsoft privacy statement for more information.

.NET Foundation

This project is supported by the .NET Foundation.

Projects we like and collaborate with

Frameworks and libraries in generated code not created by our team



You can’t perform that action at this time.