Hi WPF team! I work on Windows Template Studio. Windows Template Studio (WinTS) is a Visual Studio 2019 Extension that accelerates the creation of new Universal Windows Platform (UWP) and Windows Presentation Foundation (WPF .NET Core 3.1) apps using a wizard-based experience.
For our next release we are adding an option to our wizard to enable CodeBehind support for WPF apps. This will allow a user to create a WPF app using the CodeBehind framework straight from our wizard. Since the templates we create have to ensure best practices, we are asking for validation from the WPF team of the template we plan to ship with our product.
In this link you can find two versions of the approach. One is using a data binding approach and the other is not using data binding. This app is a simple WPF app containing a:
Main Page
Master/Detail Page
Settings Page
Please let us know which is your preferred approach as the one that ends up in our wizard will be what our users reference for future implementations of WPF apps using CodeBehind.
Hi WPF team! I work on Windows Template Studio. Windows Template Studio (WinTS) is a Visual Studio 2019 Extension that accelerates the creation of new Universal Windows Platform (UWP) and Windows Presentation Foundation (WPF .NET Core 3.1) apps using a wizard-based experience.
For our next release we are adding an option to our wizard to enable CodeBehind support for WPF apps. This will allow a user to create a WPF app using the CodeBehind framework straight from our wizard. Since the templates we create have to ensure best practices, we are asking for validation from the WPF team of the template we plan to ship with our product.
In this link you can find two versions of the approach. One is using a data binding approach and the other is not using data binding. This app is a simple WPF app containing a:
Please let us know which is your preferred approach as the one that ends up in our wizard will be what our users reference for future implementations of WPF apps using CodeBehind.