First Ring Daily Live: Let’s jUWP to the Build Conclusion

Subscribe: RSS | YouTube | iTunes | Google Play

On this live edition of First Ring Daily, we dive into the future of UWP, the outcomes of IO, and the wrap-up of Build.

Windows Intelligence In Your Inbox

Sign up for our new free newsletter to get three time-saving tips each Friday — and get free copies of Paul Thurrott's Windows 11 and Windows 10 Field Guides (normally $9.99) as a special welcome gift!

"*" indicates required fields

This field is for validation purposes and should be left unchanged.

Tagged with

Share post

Please check our Community Guidelines before commenting

Conversation 2 comments

  • StevenLayton

    11 May, 2019 - 5:48 am

    <p>JUWP. I see what you did there 🙂 </p>

  • Piyer

    11 May, 2019 - 10:59 am

    <p><br></p><p>It will be great if there is a bit of clarity on the generalized statement UWP is dead. Is it like the king is dead, long live the king?</p><p><br></p><p>Not in the UWP forever camp. However, in the modernization/.NET transformation, have gone though the pain in implementing UWP and have kept up with upgrading through the .NET iterations, now benefiting with the new capabilities with .NET iterations</p><p><br></p><p>In the simplest sense the UWP application is a scalable application across windows devices as well as iOS and Android devices using Xamarin. </p><p><br></p><p>UWP consists of multiple components for the modern windows O/S, typically XAML control, then Model, View Model or MVVM. The access to System.(dot) and other parts of the o/s was limited, which is now greatly enhanced through .NET 2.x/3.x. This does not mean that the new .NET standard compiled WPF/win32 applications can access directly the system files like legacy apps. they have to follow the similar rules which is the foundation of .NET standard and the new Windows.</p><p><br></p><p>Currently UWP apps can be published in private store similar to win32 applications and for businesses listed through Microsoft AppSource. Applications on Win IoT is .NET core only , which is UWP far as I know (because that is what we are doing now)&nbsp;</p><p><br></p><p>As I see it, the XAML part of it still very much part of the open sourced WinUI, where the UI components are developed in open source. Old WPF applications cannot scale and even with compiling in .NET standard, the WPF applications has limited scaling capability and will never scale seamlessly across devices (Scott Hunter session in Build). Some WPF parts which cannot be compiled with the new .NET has to use the XAML islands bridge.</p><p><br></p><p>The new WebUI which is also open sourced, will be in tandem with WinUI dev</p><p><br></p><p>The biggest fundamental advancement in the Web in the last 15 years is WASM, a W3 standard which Microsoft is implementing through Blazor with the same Xamarin Mono (a lot of work behind the scenes) to a merged implementation in .NET 5. Hopefully with the client side implementation of Blazor in .NET 5, this will bring enormous capability for LoB applications.</p><p><br></p><p>PWA has its place, however, for complex LoB applications, it is not going to be anywhere close to Blazor server or client applications, especially, for companies already using the Microsoft .NET stack</p><p><br></p><p>The .NET 5 is something to look forward to. Underneath, it will still have 2 BCLs one for regular and one for mobile (Miguel de Icaza session in Build).</p><p><br></p><p>So Paul, my request to you is which or all of UWP is going to be dead?. This will also give us a heads up in our own planning too.</p><p><br></p><p>Thanks in advance</p><p><br></p>

Windows Intelligence In Your Inbox

Sign up for our new free newsletter to get three time-saving tips each Friday

"*" indicates required fields

This field is for validation purposes and should be left unchanged.

Thurrott © 2023 Thurrott LLC