WinUI 3 is a new, cross-platform UI initiative from MS that has as a goal to separate the UWP UI/Application framework away from Windows.
Recently Nick came across a twitter thread talking about WinUI 3.0 (WinUI3) and how it failed to live up to expectations. Hopefully @JaykeBirdCoding won’t mind him going through his tweets and providing his thoughts. @JaykeBirdCoding!
Summary: You need to look into both Uno and outside the .NET ecosystem if you’re serious about cross platform.
Culled from reams of Microsoft documentation, here’s a high-level summary of what’s new for performance, networking, diagnostics and more, along with links to the nitty-gritty details for those wanting to dig in more.
The final topic in our .NET 5 Breaking Changes series is WPF and Windows Forms. These desktop technologies were unavailable before .NET Core 3.0, as earlier versions of .NET Core focused on web-based applications via ASP.NET Core.
Mads Torgersen writes: With every new version of C# we strive for greater clarity and simplicity in common coding scenarios, and C# 9.0 is no exception. One particular focus this time is supporting terse and immutable representation of data shapes.
It is always fun to play with new toys! This article from Julio Sampaio introduces you to Blazor – Web pages done in C#.
Blazor stands for Browser + Razor, which gives you an idea of what’s behind the new framework. Razor is the ASP.NET programming syntax that Microsoft uses to create its C# (or VB.NET) dynamic pages. Now, you can create web applications using only C# and run them in a web browser.
Microsoft ships .NET 5.0 Release Candidate 1 (RC1). It is a near-final release of .NET 5.0, and the first of two RCs before the official release in November. RC1 is a “go live” release; you are supported using it in production.