News

Uno Platform 3.0 Preview 1 Announced The new release enables WinUI 3.0 Preview 1 applications to run on iOS, Android, Web and macOS. We are pleased to announce the general availability of Uno Platform 3.0 Preview 1. The new release enables software developers to reuse the same code from their WinUI 3.0 Preview 1 – built applications and take them cross-platform to iOS, Android, Web and macOS by using Uno Platform. In turn, the code reuse produces great time savings as only single code-base needs to be developed and maintained, as opposed to five separate ones. Uno Platform team believes the Windows 10 development platform provides the most productive developer experiences, as well as the most delightful end-user applications. The time-tested security and application models as well as accessibility standards enable developers to simply leverage past investments made and to focus at implementing the business case at hand. WinUI is the modern native UI platform of Windows which makes it easy to build modern, seamless UIs that feel natural to use on Windows devices. And with Uno Platform those very same experiences can be taken to iOS, Android, macOS and Web (WebAssembly). “We are delighted to see WinUI 3 reach

Credit: This article originally appeared at https://jaylee.org/archive/2020/04/29/notify-property-changed-with-rosyln-generators.html, written by Jerome Laban. In a design meeting far, far away, source generators were designed to be part of C# 6.0, but sadly never came to be. At the time, wanting that source generation feature pretty badly, I went on implementing the specification which later became Uno.SourceGeneration, and it turns out it was the right decision to stick with a very similar API. I could port the INotifyPropertyChanged (INPC) generator I built a while back that uses Uno.SourceGeneration package, convert it to use Roslyn’s shiny new C# 9.0 feature in a matter of minutes. Amazing! The INPC Generator As a quick refresher, the generator works by allowing the creation of a class this way: partial class MyClass { [GeneratedProperty] private string _myProperty; partial void OnMyPropertyChanged(string previousValue, string newValue) { Console.WriteLine($”OnMyPropertyChanged({previousValue}, {newValue}”); } } You’ll notice here that the property is not visible at all, and it will be assumed that the generator will recognize the GeneratedPropertyAttribute and do the rest of the work for the author of the class. The generator could then produce something like this: partial class MyClass : INotifyPropertyChanged { public string MyProperty { get => _myProperty; set { var

  The performance improvements made in Uno Platform 2.2 when compared with 2.1 are spread across multiple categories: Memory pressure, with 40% of arrays reuse try/finally optimizations for WebAssembly, with 10x improvements GC Handles pressure, with 2.8x over reusing handles JavaScript tweaking, ranging with 20% and 10x faster operations Finalizers cost, with 4x improvement in objects creation UP NEXT IN 2/3 : Last night we tweeted about a WebAssembly improvement which we believe will give further 35% boost to interpreted mode performance. We will include this improvement in Uno Platform 2.3 or later. For the Windows Community Toolkit DataGrid, this translates to a 14% increase in load time performance under WebAssembly. We’ve been looking at performance in order to optimize runtime performance for all platforms, and in particular for WebAssembly. There are lots left analyze in different parts of the framework to enhance the experience for the DataGrid, specifically. Memory Pressure Updates (40% of array reuse) Memory pressure is an important part of the performance characteristics, and in recent iterations of the .NET BCL, the System.Memory package has provided many tools to help. One of tool is the ArrayPool class, which allows the renting and releasing of arrays of at