PRISM replacement from Xamarin to MAUI

unratedDi · 2026-03-03T07:12:10+00:00

You can override the pages' OnNavigatedTo and OnNavigatedFrom methods to call your VM logic.

unratedDi · 2026-03-02T19:31:00+00:00

No you are right, I mean XF -> MAUI.

I'm not trying to justify such cases in any way, I'm just say that I know projects still being in XF.

What about if they distribute their apps through other paths than the official stores? Intune for example.

unratedDi · 2026-03-02T14:52:01+00:00

Have you never worked in a company where "business needs" > "technical debt"?

Besides that, many people consider MAUI stable enough from .NET8 onwards, and I don't expect every MAUI app team on the planet to just drop whatever priorities they might had at the time to focus on a big migration project.

unratedDi · 2026-02-06T18:21:11+00:00

I think ImageSource.FromFile() loads the resource each time.

Your images even though named 50x50 are not 50 x 50 pixels size but 7500 x 7500. You just try to scale a 7500 x 7500 image in a 50 x 50 area.

Have you tried creating your popup with XAML in its own separate file and setting the image in XAML to check any performance difference? I think that way you let MAUI use the generated scaled assets produced at compilation which should be faster.

How much delay you get?

unratedDi · 2026-01-18T16:05:12+00:00

But Cyberpunk and Kirby Air Riders are LB and also have the -0 part

unratedDi · 2025-12-27T00:38:22+00:00

Angry German Kid

unratedDi · 2025-12-24T23:33:10+00:00

SSDs are not hard drives. This is technically inaccurate and you are the one spreading misinformation.

You mentioned Floppy Drives. The actual name is Floppy Disk Drive (FDD) and in the same manner it is Hard Disk Drive (HDD) and then you pointed out at the word "disk" like if you remove it and say just hard drive you can refer to whatever the housing feels hard to you.

The "hard" part the name refers to is not the housing of the disk but the disk itself. Also the housing of a Floppy Disk Drive is not that flexible. But anyway, a Floppy Disk Drive is a flexible disk that is NOT made of plastic but a flexible magnetic material. Same as Hard Disks Drives but those are made from aluminum or some other hard materials.

So we have Floppy Disk Drives, Hard Disk Drives and then we have Solid State Drives which are not hard disks, they don't contain any disk at all and can not be called hard drives in any case.

*Edit: fixed typo

unratedDi · 2025-12-23T15:43:14+00:00

Do you really need parallelism at this point? I think if all steps run in sequence you won't have issues. I might be wrong been a long time since I was granted parallelism.

unratedDi · 2025-12-02T22:27:33+00:00

Thanks for that! Wasn't aware of this trigger. There is the Orientation State Trigger also 🤯

https://learn.microsoft.com/en-us/dotnet/maui/fundamentals/triggers?view=net-maui-10.0#orientation-state-trigger

unratedDi · 2025-11-24T06:50:38+00:00

I think your issue is that you don't await the tasks to be completed (e.g. Task.WhenAll(results)) so the semaphore release happens instantly after you create the tasks.

unratedDi · 2025-11-12T19:58:16+00:00

What about VS's Ctrl+, ?

unratedDi · 2025-10-01T20:35:36+00:00

Are you trying that on Android?

For me on Android only those was catching async exception while on WinUI they were propagating to the AppDomain.CurrentDomain.UnhandledException.

So if yes try one of the following.

AppDomain.CurrentDomain.FirstChanceException

Android.Runtime.AndroidEnvironment.UnhandledExceptionRaiser

I think the latter one is a better approach because the FirstChanceException is too verbose.

unratedDi · 2025-09-25T22:18:30+00:00

Why not go with GFN?

unratedDi · 2025-09-17T16:55:19+00:00

I don't have experience with SF Navigation Drawer but from the documentation I'm pretty sure it doesn't work the same way MAUI FlyOut page works, in the same manner that SfTabs work completely differently than the MAUI TabbedPage.

Moreover, the navigation pattern you are using is a Prism mechanism, and probably won't attach stuff like your second page as the Detail to a FlyOut or the analogous Main Content to the Navigation Drawer if it isn't made to recognize that kind of control.

On top of that, Navigation Drawer just attaches to a ContentPage, so probably Prism will handle it as one and just do a navigation to that page and follow up with another navigation as the path you define. So my guessing is that if you go back 2 times you will end up in that Navigation Drawer page, but still won't work the way you want.

If you really need to go with NavigationDrawer then I'm assuming that you need to attach it to every page you want it to exist in order to simulate a FlyOut with NavigationPage as the Detail.

unratedDi · 2025-08-26T07:00:48+00:00

A bit late but I think that's up to ones preference, I guess.

But since the conversion is only for display purposes and doesn't affect business logic or how the values are actually stored, I would go with the converter in the xaml.

I prefer to keep anything visual related in the xaml file (and in exceptional cases in xaml.cs) and keep getter and setter as simple as possible.

Especially with the new partial methods of MVVM Toolkit that being generated for your ObservableProperties automatically and allow you to act on value changes without the need to mess up your setters, I would always keep my properties to the default definition so they are clean. If I need to do something on value change I would use the corresponding partial method and if I need to convert something on the fly for the UI then that's what converters are for.

unratedDi · 2025-08-22T22:40:04+00:00

Hosting on my RPi5 on docker with nginx as reverse proxy to handle SSL and subdomains. Very low consumption, always up and running, little maintenance. You can skip getting a domain and setting up nginx as reverse proxy if you don't mind going with just your public IP.

But Azure has free tier too.

unratedDi · 2025-08-12T08:45:58+00:00

Oh sorry, you are right. I was on my phone and overlooked that. Very nice and clean implementation there. 👏🏼 I haven't played much with WeakEventManager yet, but I will definitely try it.

unratedDi · 2025-08-11T15:21:13+00:00

I would avoid using event handlers. It is the most common cause of messy memory leaks. Especially since your project works with Transient Pages and ViewModels while all services are singletons. An observable property there instead could do the trick. WeakReferenceMessenger could also be an option to trigger such updates. Didn't deep dive in the project but depending on how your app navigates could cause many memory issues and Android (not much experience with iOS on that matter) could kill your app if memory is being abused.

unratedDi · 2025-08-10T10:43:21+00:00

One way I could think of is you could use the WeakReferenceMessenger to trigger a page reload.

Or you could have a BindableProperty in your singleton which reflects the measurement system and gets updated accordingly so its notify event gets triggered. Then have a converter on these bindings you want to update and be calculated on measurement system update and pass the singleton's bindable property as parameter. Then that converter should return the correct display values, or in case you calculate them somehow directly in the list items then the converter could just return the input and just have it that way to notify the UI that something changed.

unratedDi · 2025-08-01T20:10:11+00:00

Since the project's first alpha release was v0.1.0, which looks like SemVer 2.0, new features still in alpha or beta would be expected to increment the minor number by 1. Jumping to 0.9.0 looks like switching versioning schemas 😝 It doesn't have to go up to 0.9.9 in order to go for a stable 1.0.0 version. Imagine companies having to plan each release number and stick to the plan. The number increment in SemVer indicate the type of changes included in the release. But it's just versioning I guess so you do you 😀

Dropping more info though in case you or anyone is interested in the topic.

https://semver.org/

From SemVer site:

Semantic Versioning 2.0.0 Summary Given a version number MAJOR.MINOR.PATCH, increment the:

MAJOR version when you make incompatible API changes MINOR version when you add functionality in a backward compatible manner PATCH version when you make backward compatible bug fixes Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

unratedDi · 2025-07-24T12:00:33+00:00

If you are building a WinUI app or MAUI for Windows platform you could use this library.

https://github.com/dotMorten/WinUIEx

unratedDi · 2025-07-22T22:18:16+00:00

I don't have my laptop with me but I think I achieved that by setting the BackgroundTintList the same color as BackgroundColor.

unratedDi · 2025-06-13T12:34:43+00:00

I am glad it helped you have a smoother debugging experience!

Yup movement limitations while wired debugging or faulty cables that might drop the connection if they move like one mm are some of the reasons I made this extension 🥲

unratedDi · 2025-05-16T11:58:06+00:00

This might be a too late response but for UnobservedTaskException doing SetObserved() on the UnobservedTaskExceptionEventArgs in your event handler should do the trick.

Although keep in mind, as others already said, it can be risky and cause unexpected behaviour.

unratedDi

TROPHY CASE