Thanks, Gerry. My WPF application code was fairly consistent in its application of Binding with commands and converters, and I'd like to continue that level of consistency as I refactor it to WinUI 3. I'd like to take advantage of the x:Bind performance improvements, but also remain consistent in the way it's used. In other words, I'd prefer to continue to wholly use Binding (to DataContext) with traditional commands and converters, wholly use x:Bind (to code-behind objects) with traditional commands and converter classes, or wholly use x:Bind with functions (no commands or converters). This may not make sense or be possible, I just haven't gotten far enough into it to tell. So far I haven't found any showstoppers, and that's why I'm curious. But I'm also only about 10% into it.

I know commanding and converters have been a staple of MVVM pattern and XAML interfaces, but it seems like WinUI 3 is moving away from those, particularly in terms of the functionality offered (direct binding to functions and events) and seemingly encouragement in the documentation to use them instead of commands and converters. I'm in the middle of refactoring a WPF application to WinUI 3, and after writing several XAML pages, it looks like it's going to be possible to avoid commands and converters altogether. So is it an MVVM sin to wholly replace commands and converters with x:Bind functions?

Randy

Thanks, Gerry. The available in-depth information on MAUI is spotty, but from what I understand one possible path is to start refactoring the WPF app into Xamarin now, and then there will be update tools (part of VS?) that should make porting from Xamarin to MAUI more straightforward. My hope was that someone has already created a tutorial or video that took a specific look at what it would be like to go from WPF directly to MAUI. I'm sure there are some devil-in-the-details issues that's just not being discussed in the plethora of "Hello World" .NET6/MAUI presentations right now. I found one YouTube video here, but the audio is hard to follow. It's the right idea, but I was hoping for more of these. As for needing a Mac, I think it can compile the project, but there's no emulator for testing in VS right now. This is all new to me. I have a decade of learning to catch up on.

I'd like to port my WPF/.NET6 app to MAUI so I can target MacOS. I know MAUI is still a work in progress until next spring, but are there any good materials specifically on porting WPF to MAUI available yet? FYI, in the research I've done so far, these are the biggest differences/issues I've found. 1. Control properties are not directly accessible and must be set with handlers with an IF branch for each targeted platform. 2. I'll have to learn the Xamarin flavor of XAML (I assume it's similar to WPF XAML). 3. I'll have to learn how to deploy MAUI apps. I've been using ClickOnce up to this point. 4. I'll need to buy a Mac and use Visual Studio for Mac to compile for the Mac OS target.

I have an XML document that needs to pass through 4 users hands, each using the public key to encrypt and send it to the next person. The public keys and private keys are stored in the XML file, with each user's private key being protected by SYMMETRIC encryption to which they know the password. The .NET EncryptedXML class does not seem to handle this case, specifically the .encrypt and .decrypt methods of this class do not allow me to pass in an ASYMMETRIC key. Am I left to encrypt the necessary XML elements using the "regular" encryption classes, or is there a way that I'm not seeing? TIA, Randy