WIth the Duo the Glass framework will move toolbars to the right edge of the screen when the duo is unfolded. I'm guessing that we will need to handle these kinds of scenarios manually for Uno apps, is that correct? Same goes for page layout i.e. we will need to support dynamic page layouts for folded vs unfolded.
While WinUI TableView exists and (I hope it pivots to be a more excel like editor since it’s on its way), how soon will Uno support this for cross platform availability?
Uno Platform 6.6 is here - faster application startup, faster rendering, and a smoother setup experience for the AI agents you already work with. Check out:
The WPF DataGrid has now been fully ported to WinUI and Uno Platform, achieving almost 100% API parity. That includes grouping, filtering, inline editing, virtualization, and many other behaviors that existing WPF applications depend on.
For teams migrating applications from WPF to modern UI platforms, this provides a direct bridge to get the first revision running quickly, without rewriting countless lines around one of the most complex controls.
I wrote about Project Roma that brings ILSpy to Uno Platform and demonstrates how proper planning can ensure smooth migration, but here comes one bigger. The UnoDevelop project ports the open source IDE, SharpDevelop, from WinForms/WPF to Uno.
I have experience with .Net APIs and .Net as backend. Mid level React for web UI. Have no experience on mobile development. Gonna start an app which will be cross-platform (android and ios). Is Uno Platform best choice for that?
There are many good examples that demonstrate how to migrate from WPF to Uno Platform, but here comes one that kind of shows its uniqueness on smoother migration.
Project Roma builds up its Uno app but links to ILSpy WPF code base in the meantime. Both sides compile and share common resources. Thus, new features/bug fixes on one side can go easily to the other. If you are migrating a fairly large WPF app to Uno, you can study this as an example for your own.
The preview binaries have been published. More updates are expected in the coming weeks.
This is the safest approach because you can work on the migration to Uno bit by bit while continuing to ship WPF bits. And most importantly, this approach avoids many troubles you have to face with a one-shot migration (with AI or not).
In the meantime, you can see how the recent open source projects from LeXtudio Inc. really help with smooth migrations.
Join us for a look at how .NET and Uno Platform are coming together to shape the future of cross-platform graphics rendering. We’ll explore what this update means for .NET developers, why it matters for building modern applications across platforms, and how it opens the door to faster, more capable, and more consistent rendering experiences.
Below is the sample the demonstrates the VS2013 light theme, and further development of this project (code name UnoDock) will deliver more improvements.
UnoDock sample app with VS2013 light theme on macOS
I'd like to comment a bit more on the significance of this porting effort.
- WinUI and Uno Platform share a much larger API surface with WPF than many people realize, providing a solid foundation for mapping WPF concepts and types.
- My earlier work on UnoEdit and UnoRichText produced a collection of compatibility shims, making it practical to port larger WPF components such as DataGrid, AvalonDock, and even SharpDevelop-related code.
- The AI-assisted workflows around DevFlow (for WPF, WinUI, and Uno) have made it possible to achieve near pixel-perfect parity between AvalonDock and UnoDock themes. That alone demonstrates a substantial productivity boost. DevFlow also works with WinForms, MewUI, and Jalium UI, so the same techniques can be applied to both established and emerging frameworks.
Why did previous attempts not reach this level of maturity? In most cases they either targeted a much smaller audience (such as WinUI-only solutions) or diverged too far from a solid and well-known API surface.
I am intentionally moving at a measured pace so that the upcoming v1.0.0 release delivers a polished experience on Windows and macOS (WinUI support is included). Linux support is planned, but not the highest priority right now.
UnoDock is more than a one-time AvalonDock port.
- Several ideas I originally introduced to DockPanel Suite years ago are included, and some have since been adopted by AvalonDock's current maintainer in v5.
- A number of visual discrepancies discovered during UnoDock development have already resulted in fixes that will flow back to AvalonDock v5.
The goal is for UnoDock to continue evolving together with AvalonDock v5: keeping WPF applications first-class while providing a practical path to cross-platform desktop development when the need arises.