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.
Перейти к файлу
Clint Rutkas 3a9f1aed04 Create changelog.md 2017-05-22 13:07:30 -07:00
_build avoid folders 2017-05-19 02:09:34 +02:00
code Handle erros when sdk not present 2017-05-19 15:48:10 +02:00
design/Assets Adding logo 2017-04-27 14:47:32 -07:00
docs Create changelog.md 2017-05-22 13:07:30 -07:00
samples/activation Removed temporary key from sample app 2017-05-08 10:20:17 +02:00
templates Merge pull request #368 from Microsoft/Issue#357 2017-05-18 19:41:23 -07:00
.editorconfig Added .editorconfig to generated projects and big.sln 2017-04-15 16:52:48 +01:00
.gitattributes Moved templates test to new solution 2017-01-19 09:40:55 +01:00
.gitignore Changed TestAtifacts name 2017-03-06 09:14:25 +01:00
CONTRIBUTING.md markdown cleanup 2017-04-30 15:37:12 -07:00
LICENSE.md Lots of adjustments for documentation and formatting. 2017-04-10 20:36:15 -07:00
README.md Update README.md 2017-05-17 12:01:19 -07:00

README.md

Windows Template Studio

Windows Template Studio is a Visual Studio 2017 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.

Example scenario: I need an app that uses MVVM Light, uses master detail, can suspend and resume, settings, maps on one of the pages and will need Azure hub notifications. It will need a background service that does a query every 5 minutes.

Windows Template Studio screenshot

Build Status

Env CI Templates Publishing Extension Publishing Full Templates Tests
dev CI Build Templates Publishing Build Extension Publishing Build Full Templates Tests
pre-release CI Build Templates Publishing Build Extension Publishing Build Full Templates Tests

Features

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

  • Project type: First, how do you want your app's UI navigation to behave? We currently support three project types: basic, navigation pane, and pivot and tabs
  • App framework: Next, what coding pattern do you want to use in your project, we currently support three common patterns: code behind, basic MVVM, and MVVM Light
  • App pages: To accelerate app creation, we provide a number of app page templates that you can use to add common UI pages into your new app. We currently include page templates from the blank page to the common layouts (e.g., master/detail, tabbed, web view) to pages that implement common patterns (e.g., app settings, map control). Using the wizard, add as many of the pages as you need, providing a name for each one, and we'll generate them for you.
  • Windows 10 features: Lastly, you 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 application lifecycle (settings storage, suspend and resume), background tasks, and user interaction (app notifications, Live tiles, and Azure Notification Hub).

Once you select the attributes you want your new UWP app to have, you can quickly extend the generated code.

Known Issues

The following are known issues and may affect your use of Windows Template Studio. These will be addressed in the next few days.

  • You must be online the first time you use the wizard to generate an app or no templates will be loaded. #311
  • Only compatible with Windows 10. You cannot use this if running VS 2107 on an older Operating System. #357

Documentation

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

Contributing

Do you want to contribute? Here are our contribution guidelines.

Principles

  1. Generated templates will be kept simple.
  2. Generated templates are a starting point, not a completed application.
  3. Generated templates once generated, must be able to be compiled and run.
  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/librarys creator.
  6. All features will be supported for two current Windows SDK for Windows 10 release cycles or until another principle supersedes it.
  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

License

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

Code of Conduct

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Privacy Statement

The extension does log basic telemetry for what is being selected. Please read the Microsoft privacy statement for more information.