Everything you need to know about WinUI

The Discussion

  • User profile image
    It would be helpful to get more information about where the UWP development experience is headed.

    Will we retain the .Net Native compiler when using WinUI 3? Specifically, will the UWP toolchain generate native code from C# code. This is an important consideration from a perf perspective and protection of code since .Net IL can easily be converted back to source code.

    Will Microsoft publish samples for UWP that show how to integrate properly with the Visual Studio designer? You are now publishing such samples for WPF and the new designer, yet this was never been addressed for UWP.

    Is the Appx container going to stay the same with WinUI3?

    Is the Microsoft App store going to stay the same? If not, what changes can we expect and what are the new terms of use?

    Will there be a fully non-restricted mode for UWP? This should be added given UWP should be the superior way of building a Windows desktop app, especially given Win32 will have access to the entire WinRT API. Please add this as a capability.

    Please show some love for the UWP side of thigs. UWP needs access to the Win32 multimedia timers and other OS services so UWP can be used to create any sort of desktop application. Perhaps make the multimedia timers a special capability for MIDI software that might still be functional in a security sandbox. Access to low level OS features was a gaping hole in the feature set available to UWP. Clearly, Microsoft is no longer worried about things like battery life for a certain class of application.

    Please retain the sandbox features of UWP. UWP is still the safest and coolest way for novice users to install apps on their systems.

    Please stop redirecting and or replacing UWP searches with Xamarin content.

    Please provide a centralized method for surfacing WinUI 3 and WinRT API issues. Preferably, a GitHub issues section somewhere.

    Lastly, the historical retrospective did skip over Silverlight and the many iterations of XAML on Windows Mobile. Failures often provide some of the most insightful historical references. Let's not forget them.

Add Your 2 Cents