Every year, we’re forced to revisit this topic, so why not just have some fun with it? Is the Universal Windows Platform (UWP) (still) dead?
Recent UWP Stories
Microsoft continues to baby-step around the obvious, but it has officially deprecated the Universal Windows Platform (UWP).
Microsoft today announced the availability of the Windows Community Toolkit 7, the latest version of this set of tools for Windows desktop developers.
UWP apps like .NETpad natively support Windows 10’s Dark and Light app modes (themes), but we need to tweak that support just a bit.
Today, we’ll implement .NETpad’s Auto Save functionality, which will work nearly identically to the way we did it previously in WPF.
I think I’ve finally found a reliable way to prompt the user to save an unsaved document if they try to manually close the app.
This time, we’ll implement .NETpad’s text zooming capabilities, fix the application name, and add a new application icon.
For this installment of our UWP project, we’ll implement Find, Find Next, Find Previous, Replace, and Replace All with a fun new custom dialog.
With File Open and the Save prompt out of the way, we can move forward to the other app commands that involve file operations: New, Save, and Save As.
In this fourth installment, we’ll get started on file operations and custom dialogs, both of which occur asynchronously in UWP.
In this installment of the UWP Notepad project, we’ll implement the non-font user settings and a workaround for a UWP weirdism that had me stumped for days.
In this second installment, we’ll use C# to implement user settings related to fonts, word wrap, the command bars, and auto save.
Like some real developers, I’ve gone through what I call the three stages of irrational exuberance with Project Reunion only to land back in reality.
Project Reunion is a modern replacement for UWP and a way to use APIs that were locked into UWP in other developer frameworks.
After years of silence and misinformation, Microsoft finally made it official: It is “unifying access” to Win32 and UWP APIs.
Well, here’s the final nail in the UWP coffin: At Build 2020, Microsoft will finally describe how it plans to move past this platform disaster.
I had almost given up on the UWP version of .NETpad multiple times because of difficulties with asynchronous operations.
For the UWP version of .NETpad, I’m trying to rethink the user experience in way that respects the strengths of this platform.
My struggles with the Universal Windows Platform (UWP) continue. A key contributor: Asynchronous file operations and pop-ups.
After going down a few rabbit holes, I think I’ve finally arrived at a UI that makes sense for the UWP version of .NETpad.
After experiencing many frustrations, I had an interesting breakthrough with UWP, mirroring an earlier and similar success with WPF.
I spent a lot of time researching UWP and Xamarin Forms over the weekend and decided to renew my efforts to port .NETpad to UWP first.
The Universal Windows Platform (UWP) isn’t particularly well-suited to traditional productivity applications.
So, we need to discuss this week’s news about the end of ad-based UWP app monetization through the Microsoft Store.
Microsoft’s relationship with UWP has been estranged, at best, in the past couple of years. But the future of UWP doesn’t look all that bright.
Apple is looking to build the next-generation of Windows media apps for its services as the company pushes to get Apple TV+ on the Xbox.
Microsoft is evolving the Windows 10 app development platform by turning its back on its original strategy.