My struggles with the Universal Windows Platform (UWP) continue. A key contributor: Asynchronous file operations and pop-ups.
Recent Premium Stories
Microsoft signals that Windows 10X and its simplified new user interface and container-based architecture is too important to screw up.
I’ve spent the past several months forcing myself to access my primary web apps differently, opening up new browser options.
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.
Happy Friday, and Happy April, too. Here’s a lengthy and diverse set of questions to kick off the weekend.
After experiencing many frustrations, I had an interesting breakthrough with UWP, mirroring an earlier and similar success with WPF.
There is an interesting dynamic between parenting and the Internet where it can be tough to balance access to information but not letting usage distract from other activities.
With their backs to the wall and nearly everything aligned for them to fail, the Surface team had to find a better solution.
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.
With the WPF .NETpad now roughly functionally identical to the WinForms version, I’m starting to think about additional unique features.
Even with Spring in full motion, this weekend will be a lot less interesting than usual. Thanks, Coronavirus!
Let’s add Find, Find Next/Previous, Replace/Replace All, and Auto Save and make the WPF version of .NETpad functionally complete.
Thanks to a variety of factors, I’ve pulled the trigger on something I’ve been investigating for a long time. I’m switching to Mint Mobile.
With the release of iPadOS 13.4 today, Apple has finally done what its fans and critics alike have been begging for.
In this installment, we’ll implement several more Edit menu items in the WPF version of .NETpad and create a custom Input Box.
In this installment, we’ll create an About box for the WPF version of .NETpad and start building out the Edit menu.
In this installment of the development of the WPF version of .NETpad, we’ll create a custom Font dialog using XAML and data binding.
Spring is finally here, though the Coronavirus has dulled the celebration. But here’s a great set of questions to kick off the weekend.
In this installment, we’ll get all of the save operations out of the way, plus add New and New Window operations.
In 2003, Longhorn promised to change the world forever. In 2020, Windows 10 can only promise tiny, subtle changes to a mature platform.
I’ve been arguing for years that the iPad could never replace the PC until it provided all of the features that PC users demand.
Building on the progress we made last time, let’s add open file functionality, textbox events, and theming support to .NETpad.
This time, we build out the Format and View menus, add word-wrap and status bar toggling, and implement Zoom using commands.
In part two of this project, we’ll add Exit and Print commands, implement several textbox settings, and use the real application name.
For this second project, we’re going to recreate .NETpad using C#, Windows Presentation Foundation, and .NET Core 3.1.
I don’t believe rumors that the Pixel 5 will be a mid-range handset instead of a flagship. But that is exactly what Google should do.
The C#/WPF/.NET Core 3 version of .NETpad is now complete and feature-comparable to its Windows Forms predecessor. So what's next?