Category Archives: wts

Auto Added by WPeMatico

Windows Template Studio 2.0 is now available!

Windows Template Studio has released our 2.0 release and can’t wait for everyone to create some amazing applications with it. Template Studio is an open source project whose sole goal is to get you building applications quicker with best practices with a solid initial code base.
We’re extremely proud of our community driven project and the massive contributions / partnerships we’ve had with you over the past year since we launched.

How to get the update:
There are two paths to update to the newest build.
Already installed: Visual Studio should auto update the extension. To force an update, Go to Tools->Extensions and Updates. Then go to Update expander on the left, and you should see Windows Template Studio in there, and click “Update.”
Not installed:Head to https://aka.ms/wtsinstall, click “download,” and double click the VSIX installer.
What has happened under the hood?
We’ve done a lot of work improving the user interface and being sure we’re fully accessible for all developers. By partnering with the Visual Studio team, we feel the new interface is faster and more approachable. We’ve improved our template updating experience, our actual templates and much more. Our wizard also now detects dark, light and high contrast modes of Visual Studio.
In addition, once the next update to Windows 10 is released, we’ll adopt the platform NavigationView control over the UWP Community Toolkit’s great Hamburger menu control, which already does do a smart flip between their classic and the platform control. We’re currently working on documentation to aid in that transition between the existing control and the new platform control as well.
Documentation, everyone’s favorite friend
We are pushing hard on improving our docs and will continue to do so. Over time, most of our docs will migrate to docs.microsoft.com that cover our templates and using the actual wizard. The docs that will stay on WTS’s GitHub will be docs on modifying the engine or creating a template for the wizard to consume.
Future progress, getting updates and community interaction
Moving forward, we’ll continue to push hard and add in new features and templates.
Some of our largest additions, bugs and best feature ideas came from you, the community. The WTS team are extremely honored to have been a part of this and everyone that has filed a bug to submit a PR, you should too. We encourage everyone to log bugs, submit feature requests, and contribute back at https://aka.ms/wts on GitHub.

Windows Template Studio 1.7 released!

We’re extremely excited to announce the Windows Template Studio 1.7! In this release, our two big items are Visual Basic support and Prism framework!  We love how the community is helping. If you’re interested, please head over to head over to WTS’s Github.
What’s new:
Full list of adjustments in the 1.7 release, WTS’s Github has a full changelog.

New Programming Language Support:
Visual Basic
New Framework Support:
Prism framework
Updated Feature:
URI Schema launching for Caliburn.Micro added.
Template improvements:
Tweaks for consistence across all frameworks and languages
Fix for bug where we have a toast and first time prompt crash.
Fix for JSON Helper (#1659)
Improvements to the Wizard:
Lots of under the hood bug fixes and code improvements
Changed how we handle verifying new templates. This process should be much faster now.
Improvements to Process and Tooling:
Improved unit testing for verifying templates
How to get the update:
There are two paths to update to the newest build.
Already installed: Visual Studio should auto update the extension. To force an update, Go to Tools->Extensions and Updates. Then go to Update expander on the left and you should see Windows Template Studio in there and click “Update.”
Not installed: Head to https://aka.ms/wtsinstall, click “download” and double click the VSIX installer.
Known issue
We are tracking an issue (#1532) when uninstalling / upgrading where you may get an error of “A value for ‘Component’ needs to be specified in the catalog.”
If you get this error, we need logs to help track this with the help of the Visual Studio team.  We don’t know how to reproduce it, but we know a few people have hit this scenario.
We have how to capture these logs in the tracking issue on GitHub.
What else is cooking for next versions?
We love all the community support and participation.  In addition, here are just a few of the things we are currently building out that will in future builds:
Improved user interface in-line with Visual Studio
Continued refinement with Fluent design in the templates
Work for supporting multiple projects in a single solution
Ink templates
Improved Right-click->add support for existing projects
With partnership with the community, we’ve will continue cranking out and iterating new features and functionality. We’re always looking for additional people to help out and if you’re interested, please head to our GitHub at https://aka.ms/wts. If you have an idea or feature request, please make the request!

Windows Template Studio 1.6 released!

We’re extremely excited to announce the Windows Template Studio 1.6!
In this release, we added in app scheme launch, finalized our work for localization, massive improvements in accessibility, and started our work for Visual Basic support.
What’s new:
Full list of adjustments in the 1.6 release, head over to WTS’s Github.

New Pages:
Image Gallery
New Features:
Drag and drop source
Web to App Link
Template improvements:
Minor tweaks for Fluent
Discovered a few pages that set background color
Improvements to the Wizard:
Lots of under the hood bug fixes and code improvements
Much more Visual Basic engine work
Work for supporting multiple projects in a single solution
Work to support Prism
How to get the update:
There are two paths to update to the newest build.
Already installed: Visual Studio should auto update the extension. To force an update, Go to Tools->Extensions and Updates. Then go to Update expander on the left and you should see Windows Template Studio in there and click “Update.”
Not installed: Head to https://aka.ms/wtsinstall, click “download” and double click the VSIX installer.
Known issue
We are tracking an issue (#1532) when uninstalling / upgrading where you may get an error of “A value for ‘Component’ needs to be specified in the catalog.”
If you get this error, we need logs to help track this with the help of the Visual Studio team. We don’t know how to reproduce it, but we know a few people have hit this scenario.
We have how to capture these logs in the tracking issue on GitHub.
What else is cooking for next versions?
We love all the community support and participation. In addition, here are just a few of the things we are currently building out that will in future builds:
Visual Basic support (In nightly)
Prism support (In nightly)
Improved update system to help increase speed of startup and file size download
Improved user interface in-line with Visual Studio
Continued refinement with Fluent design in the templates
Ink templates
Improved Right-click->add support for existing projects
With partnership with the community, we’ve will continue cranking out and iterating new features and functionality. We’re always looking for additional people to help out and if you’re interested, please head to our GitHub at https://aka.ms/wts. If you have an idea or feature request, please make the request!

Windows Template Studio 1.3 Released!

We’re extremely excited to announce the Windows Template Studio 1.3.
In this release, we added in app scheme launch, finalized our work for localization, massive improvements in accessibility and started our work for Visual Basic support.
What’s new:
For a full list of adjustments in the 1.3 release, head over to WTS’s Github.

New Feature:
Scheme to launch app (aka myAwesomeApp://myDeepLinksIntoMyApp?foo=bar)
Template improvements:
Default Windows theme support added to template
Files are now UTF-8 with BOM to make sure all cultures are supported
Accessibility support in templates
Improvements to the Wizard:
Accessibility support in Wizard drastically improved
Lots of under the hood bug fixes and code improvements
All needed parts for localization are built-in now (looks like we missed window to get actual localized files)
Initial VB engine work was added in.
Bug fixes
Process improvements:
StyleCop enforcements across Template and Wizard code bases
Appveyor added for pull requests to be sure we have proper continuous integration checks
Required work for .NET Foundation
How to get the update:
There are two paths to update to the newest build.
Already installed: Visual Studio should auto update the extension. To force an update, Go to Tools->Extensions and Updates. Then go to Update expander on the left and you should see Windows Template Studio in there. Click “Update.”
Not installed: Head to https://aka.ms/wtsinstall, click “download” and double click the VSIX installer.

What else is cooking for next versions?
We love all the community support and participation. In addition, here are just a few of the things we are currently building out that will be in future builds:
Fluent Design in the templates
Ink templates
Improved Right-click->add support for existing projects
Localization in the wizard
Visual Basic support
Caliburn.Micro support
Prism support
With partnership with the community, we will continue cranking out and iterating new features and functionality. We’re always looking for additional people to help out and if you’re interested, please head to our GitHub at https://aka.ms/wts. If you have an idea or feature request, please make the request!