Windowstemplatestudio: WinUI 3 UWP and Desktop Class Libraries

[JeanRoca]

WinUI 3 Class Libraries

Summary

To provide parity to the templates currently offered by WinUI 3 in the Project Reunion 0.5 VSIX, we must offer developers with the entry points in our wizard to create class libraries for both Desktop and UWP. Due to us not supporting customizations of class libraries currently, we will NOT open the WinTS wizard upon project creation and instead just generate the class library output. These templates will include the same output as these which are in the current Project Reunion VSIX:

Scope

| Capability | Priority |
| :---------- | :------- |
| Provide exact same output as the Project Reunion 0.5 VSIX | Must |
| Provide one entry point for each (Desktop and UWP) | Must |
| Will not open up the WinTS wizard | Must |

Applies to the following platforms:
| UWP | WPF | WinUI |
| :--------------- | :--------------- | :---------------|
| No | No |Yes |

[mrlacey]

To provide parity to the templates currently offered by WinUI 3 in the Project Reunion

Rather than providing _parity_, this sounds like a duplication of functionality.

I could understand this if the intention was that WinTS was a valid alternative to installing the ProjectReunion VSIX.
Is this issue an acknowledgment that WinTS will become a valid, supported alternative to the ProjectReunion VSIX and the creation of WinUI3 apps with only the WinTS extension and not the ProjectReunion extension installed is to become a valid, supported scenario?

If the need for the ProjectReunion VSIX is not being removed, what is the value in adding this? Isn't it likely to cause confusion when two similar entries exist in the new project type list?

[JeanRoca]

Is this issue an acknowledgment that WinTS will become a valid, supported alternative to the ProjectReunion VSIX and the creation of WinUI3 apps with only the WinTS extension and not the ProjectReunion extension installed is to become a valid, supported scenario?

This is exactly what we are aiming for. We are working internally to make WinTS the default experience for creating WinUI 3 apps and this would include making this a supported scenario.

[mrlacey]

This is exactly what we are aiming for. We are working internally to make WinTS the default experience for creating WinUI 3 apps

How can this be communicated more widely so appropriate feedback and input can be obtained?

[gcaughey]

I think WinTS as _a_ default experience is a great idea, but I can also see the value of keeping the current Blank App Desktop template for Project Reunion as well.

[mrlacey]

I think WinTS as _a_ default experience is a great idea, but I can also see the value of keeping the current Blank App Desktop template for Project Reunion as well.

@gcaughy If they got rid of the current blank app templates entirely I expect someone would quickly recreate them 😉

[JeanRoca]

I think WinTS as _a_ default experience is a great idea, but I can also see the value of keeping the current Blank App Desktop template for Project Reunion as well.

Don't worry, we won't be doing that ;)

This is exactly what we are aiming for. We are working internally to make WinTS the default experience for creating WinUI 3 apps

How can this be communicated more widely so appropriate feedback and input can be obtained?

We are working with the team to determine what exactly we will and will not support as well as the project changes that need to be made to WinTS for us to support this. Once we have that as a concrete plan we will make a more formal announcement.

[dotMorten]

Please keep the blank app. If I had to be honest I wish the blank app was even "blanker" (the Button and it's click handler gets quite annoying quickly)

[sibille]

While working on the templates for Desktop and UWP ClassLibraries we had the following doubts:

• Naming: We're currently using the same name as the reunion vsix: Class Library (WinUI in Desktop)/Class Library (WinUI in Uwp) and the WTS icon. Should we add Windows Template Studio or WTS to the name?
• Uwp Class Library: For Uwp Class Library creation we're showing the TargetFramework/MinTargetFramework dialog as as the reunion vsix does. We don't show this dialog for Uwp App creation and always target 2004/1809 instead. Wondering is we should do the same for Uwp Class Libraries to be consistent.

[mrlacey]

• Naming: We're currently using the same name as the reunion vsix: Class Library (WinUI in Desktop)/Class Library (WinUI in Uwp) and the WTS icon. Should we add Windows Template Studio or WTS to the name?

As not showing the WinTS wizard once the option is selected I would not include the "Windows Template Studio" in the name. The icon already serves as an indication that this is from the WinTS extension--if distinguishing between options is a concern.

• Uwp Class Library: For Uwp Class Library creation we're showing the TargetFramework/MinTargetFramework dialog as as the reunion vsix does. We don't show this dialog for Uwp App creation and always target 2004/1809 instead. Wondering is we should do the same for Uwp Class Libraries to be consistent.

If the intention is to replace the option installed with the SDK then I'd leave the selector in.
If this is intended to only be used with WinTS projects then don't include the dialog as it would risk creating something not compatible with an existing app project.
_Noting, of course, that the min & target frameworks can be changed after creation_

[sibille]

As not showing the WinTS wizard once the option is selected I would not include the "Windows Template Studio" in the name. The icon already serves as an indication that this is from the WinTS extension--if distinguishing between options is a concern.

Agree!

If the intention is to replace the option installed with the SDK then I'd leave the selector in.
If this is intended to only be used with WinTS projects then don't include the dialog as it would risk creating something not compatible with an existing app project.

Intention is to be able to add a class library to a WinTS project or a different project.

[mrlacey]

Intention is to be able to add a class library to a WinTS project or a different project.

Then I'd leave the picker in but default to the values that match what WinTS uses.