Open mrlacey opened 3 years ago
The bigger question here is "what other options are going to be added to the WinUI3 templates?" Not just framework/design-pattern, but also pages, features, services, testing, etc.?
@sibille It would be great to know which features and pages we can expect for WinUI and the associated WTS versions. I am looking for the login feature, however could not find when or which version it is expected.
@harvinders, for version 4.0 we are planning to include the following pages/features for WinUI Desktop Apps (C#):
For project type/framework options version 4.0 will include NavigationView + MVVM Toolkit and a Blank project type without any frameworks or scaffolding.
For version 4.1 we are looking into expanding on project types by adding a Blank Advanced project type that adds folder scaffolding and basic services and the MenuBar project type.
Adding @marb2000 for future plans.
@sibille It would be great to know which features and pages we can expect for WinUI and the associated WTS versions. I am looking for the login feature, however could not find when or which version it is expected.
We'll be looking at this for 5.1. Tracked by #4475.
I will go out on a limb here and suggest something else (Plain Old Projects). No MVVM, no DI, no resx file: just plain XAML with values and simple, simple bindings. Why? A lot of development is what I would call localized development. No QA team (limited testing needs), no large deployments, no layer abstractions needed, not a product. Just simple apps that support departmental business needs and are used by only a few people. They need to be very simple to maintain and understand. I gave up on this project because it is way overkill for what I need. Would love to try it again.
You can use the barebones WinAppSDK templates for that. Agreed you don't need Template Studio for your scenario.
Is your feature request related to a problem? Please describe.
The WinUI3 templates currently only offer MVVM Toolkit as an option for the framework (design pattern) when working through the wizard.
Are there plans to add more? If so, what will they be? Will there be different options for UWP and Desktop app models? Will there be different options for C# & C++?
Describe the solution you'd like
There is no public documentation clearly indicating what to expect with the WinUI3 templates and what they will contain. Adding this will allow developers to understand how they will be able to use Windows Template Studio, with WinUI3, in the future.
Describe alternatives you've considered
If no other frameworks (design patterns) are to be provided this will limit the value of Windows Template Studio in the future.
Additional context Add any other context or screenshots about the feature request here.