Wpf: Windows Template Studio + WPF with .NET Core 3.0 templates - Feedback request

[sibille]

From Windows Template Studio we are looking into adding new project templates for WPF with .NET Core 3.0 generation.
If you're not familiar with Windows Template Studio head over to http://aka.ms/wts and check out our repo, WTS is a Visual Studio extension that accelerates the new project experience for UWP.

Based on our feedback sessions at Build 2019, telemetry and conversations with the WPF team we've selected what we believe are the most wanted/important project types, frameworks, pages and features we want to start with.

We'd love to get your feedback on this list. What do you think is most important? Is there something missing for a first version? And also, is there something that doesn't feel important?

Project Types:

• Blank
• Menu Bar
• NavigationView
• Ribbon

Frameworks:

• MVVM Basic
• MVVM Light
• Prism

Pages:

• Blank
• Settings
• WebView
• MasterDetail

Features:

• MSIX Packaging
• Win 10 Theme Support
• Setting Storage / Persisting app data

[weltkante]

Looks good to me, that covers pretty much what I would expect to use myself.

[shaggygi]

@sibille This is a great start. Will there be a future transition to utilize controls/packages coming in WinUI 3.0 overtime? Thx

[alvinashcraft]

That sounds like a pretty good v1 to me as well. Adding pages with 3rd party controls like Charts or Grids can come later.

[rido-min]

there will be any themes available in this release?
Why restrict to WPF con .NET Core? Almost everything should be compatible with WPF on .NET FX, unless you use C#8 features

[mrlacey]

there will be any themes available in this release?
Why restrict to WPF con .NET Core? Almost everything should be compatible with WPF on .NET FX, unless you use C#8 features

The goal is to help people building new apps and encourage the use of new features by making it easy to use them.
Focusing on just one platform, at least at first, also helps with getting something shipped and allows gaining real-world feedback. Adding support for .NET Framework is something that could be added in the future. It's not ruled out. It's just "not yet".
If that's a blocking issue for you, an explanation of why will help shape priorities.

[TonyHenrique]

Looks good. Will there also have the F# templates?

[thomasclaudiushuber]

Looks like a good start to me. What I would like to see in the _MVVM Basic_ template is Dependency Injection set up.

[christiannagel]

Looks good. In addition to dependency injection set up with the MVVM Basic template It would be great to use the .NET Core 3.0 Host class.

[rabbitism]

Please also help to add samples of resource dictionary usage, such as different kinds of Uris.

[indierawk2k2]

Please also help to add samples of resource dictionary usage, such as different kinds of Uris.

Can you please explain a bit more what you're looking for here? What is the scenario that will benefit from this? Thank you for any additional information

• Mike

[Daniel-Svensson]

I would like to see some concept concept from the old "business application" template for silverlight.

• Login screen and maybe logout?
• Navigation between 2 additional views

maybe even with a connected service (web
/server app) where data is fetched from (but mock classes would do as well)

[rabbitism]

Please also help to add samples of resource dictionary usage, such as different kinds of Uris.

Can you please explain a bit more what you're looking for here? What is the scenario that will benefit from this? Thank you for any additional information

• Mike

Hello Mike,

When I was a WPF newbie, I struggled a lot when I tried to include some resource in my project, like

• use a resource dictionary from other compiled libraries
• in a project that is going to be compiled as a .dll, how I should reference a font file in a resource dictionary.

Things like this.

Thanks!

[SariDev]

Hi everyone,

regarding Framework's, I would like to see support for ReactiveUI.

See https://reactiveui.net/

Developing a WPF MVVM app in a reactive manner has many benefits.
Personally I had a tough time when trying to get started with the framework as the documentation is somewhat incomplete and doesn't cover some aspects in detail.

Supporting ReactiveUI from WTS could make the start a lot more comfortable and lead more developers to reactive programming.

Best regards

[rasyidf]

maybe for next release, this list of my suggestion will be good

Project Types:
MDI Application
Tabbed Navigation

Frameworks:
Caliburn.Micro ❤

Features:
Docking
Localisation Service.
Dialog Service using Vista Style

Styling
Title Bar Theme (not the default white in dark environment)
Upgraded Win 10 Fluent Style Controls
Color Accent Synchronized with Windows.

maybe this suggestion will be easy if WPF Community Toolkit can be revived and maintained again.

[leonhui]

Any way to try out pre-release version?

[sibille]

Hi @leonhui,
There is no preview yet, but we've built Mockups of what should be created for the different project types and frameworks. We'd love to get your feedback on the following issues:

Window Template Studio WPF Feedback issues

Also, big thankyou to everybody for all the input you gave!

[AzuresSunday]

MVVM Light pls.

[sibille]

Yes, MVVM Light will be part of the initial set of templates.

[sibille]

Windows Template Studio Version 3.7 shipped last week with WPF tempates.
Please head to https://aka.ms/wtsinstall to install the VSIX.
Thanks again to everybody for your feedback!!