.NET 11 MAUI Preview 7: Key Updates for Developers

Microsoft just released .NET 11 Preview 7, and it’s packed with updates for .NET MAUI that should interest any developer looking to speed up cross-platform projects. This version introduces the Passkeys API, upgrades XAML Hot Reload, and adds new Shell route templates, among other changes. If you're developing for Android, iOS, Mac Catalyst, or Windows platforms, there's something here for you.

What's New in .NET 11 MAUI Preview 7?

The Passkeys API is probably one of the biggest highlights in this release, now incorporated into MAUI Essentials. It’s designed to offer a native passkey experience across platforms like Android 14 or later, iOS and Mac Catalyst 16 or later, and supported Windows 10 versions. You’ve got Passkeys.CreateAsync for credential registration and Passkeys.AssertAsync for authentication. There's also Passkeys.IsSupported to check if a platform is compatible.

That said, don't expect the Passkeys API to take care of everything. While it simplifies client-side operations, server-side duties are still yours to handle. This includes generating challenges, providing WebAuthn options, and validating assertions or attestations. You'll need proper trust configurations, like Associated Domains on Apple platforms or Digital Asset Links on Android. Make sure your server setup is up to the task, because this API doesn’t cover the backend stuff.

Incremental XAML Hot Reload

XAML Incremental Hot Reload is another interesting update, and it’s a real change-maker from older versions. It's enabled by default for Debug builds, letting you tweak UI components without rebuilding the entire XAML. A source generator and MetadataUpdateHandler power this incremental change system. It covers property updates, adding or removing children, structural reordering, and more. If it feels awkward, you can switch back using the EnableMauiIncrementalHotReload setting. Plus, it works with dotnet watch for real-time changes, which should speed up your feedback loop.

Enhancements in Shell Navigation

Shell navigation steps up with route templates, borrowing concepts from ASP.NET Core and Blazor routing. These templates allow for detailed routing patterns, including required and optional segments. A route like product/{sku} gives you structured paths with placeholders for dynamic data. Just a heads-up: they only support absolute navigation right now. You'll need to rethink your approach if you're used to relative routing. These routes work with QueryProperty and IQueryAttributable, so you can integrate them with your current navigation logic smoothly.

Changes to the XAML source generator also mean better AOT safety. The update allows {RelativeSource AncestorType=...} bindings to compile to TypedBinding instances, cutting down on reflection use. This helps minimize issues during trimming, avoiding missing members. However, bindings like Self and TemplatedParent still rely on runtime paths. Something to be cautious about if you're concerned about keeping your application robust after deployment.

Platform-Specific Updates

Preview 7 doesn't just stop at cross-platform; it addresses platform-specific concerns too. On iOS and Mac Catalyst, handlers replace legacy renderers for NavigationPage and TabbedPage, aiming for better performance and consistency. The transition is part of a broader move to modernize MAUI’s architecture. Older renderers remain for custom implementations, so test thoroughly before making the switch.

Android developers will notice FastDeploy2 is the new default, promising faster deployment times by focusing on incremental updates, not full redeployments. This could cut down iteration times considerably. Windows developers get features like Window.StatusBarTheme and the ability to save captured media directly to the system gallery. Also, dotnet watch now supports Hot Reload on physical iOS and tvOS devices over USB or Wi-Fi, making testing on real hardware quicker.

What This Means for Developers

Expect boosts in productivity and performance with .NET 11 MAUI Preview 7. The Passkeys API simplifies cross-platform authentication, which is a big deal for security-focused projects. Incremental XAML Hot Reload might just make long rebuild times a thing of the past, a blessing in environments where rapid changes are crucial.

From my own tinkering, these updates could really streamline workflows, especially when dealing with complex UI designs or multi-platform applications. The way hot reload reduces context switching alone could improve focus. Always test new features in your existing codebase to make sure everything plays nice together.

Actionable Steps for Monday Morning

• Explore Passkeys API: Dive into the API documentation and try integrating it into your authentication system. Make sure your server can meet WebAuthn requirements like generating challenges and validating assertions.
• Test Incremental XAML Hot Reload: Turn it on in your Debug builds and see if it speeds up your development process. You can go back to the old method if needed. Watch how it deals with various UI changes in your projects.
• Update Routing Logic: Using Shell navigation? See how route templates could change your routing strategies, but keep in mind the limitations with relative navigation. Consider how this will affect your current navigation setup.
• Evaluate Platform-Specific Changes: Check out the new handlers on iOS and Mac Catalyst, and analyze how FastDeploy2 affects your Android development. Figure out if these changes make your workflow more efficient.

Limitations and Considerations

These announcements are exciting, but there are still limitations. The Passkeys API demands server-side support, and XAML Incremental Hot Reload might not be the perfect fit for every situation, especially if you're holding onto older methods. Also, the Shell route templates' current lack of relative navigation support might require altering your existing navigation flows. Managing these shifts smoothly is crucial to avoid disruptions.

Ultimately, while these updates simplify some aspects of cross-platform development, careful integration is needed to avoid workflow hiccups. As with all new tech, slow and steady wins the race. Test thoroughly and adopt incrementally to harness the benefits without the headaches. Understand what each update brings and see how it fits into your overall development strategy, so you make choices that bolster your app’s capabilities and maintainability.