Windows Development

Microsoft DevBlogs has just been federated and can be followed at @msftdevblogs@dotnet.social.

Thanks to @mapache@hachyderm.io!

cross-posted from: https://programming.dev/post/9780587

In MAUI 8.03 we had the Flyout bug where the NavigationPage Title wouldn't update from the first page you had been on. In MAUI 8.06 that bug has been fixed but has introduced a new one on Windows (sigh).

Starting on Page1 I can use the Flyout to switch to Page2. Then, on Windows, if I use Flyout to switch back to already-existing Page1 it crashes with...

System.Runtime.InteropServices.COMException (0x800F1000): No installed components were detected.

Element is already the child of another element

It works on Android, and it works if you are creating a new page each time, it just doesn't work on Windows to switch back to an already-created page (which defeats the whole purpose of having a Flyout menu - switch between 2 pages without making a new one every time).

1. Does anyone know of a workaround to this? I can't find anything that relates to this in the context of a MAUI Flyout.
2. Does anyone have a real simple Flyout template that could be used for the repro (to put in the issue I'm gonna need to create). The one I'm working on has a whole bunch of my own libraries in it, so I'm gonna need to tear them all out before I can use it to make a repro (and of course they don't provide a template, and their sample doesn't work due to different bugs - sigh).

Hello everyone. I am your mod, Donald, Founder of Smartman Apps. You can find me on Mastodon at @SmartmanApps@dotnet.social.

You can follow/post to this Community from Mastodon by following @windows_dev@programming.dev

A few rules…

1. As usual these site-wide rules apply (bear in mind this is a SFW Community)…

• Dangerous content on the instance and federated instances including phishing, spamming, brigading, unmarked nsfw, nsfw content in sfw communities, doxing, etc. is not allowed and subject to be handled by the mods or admins
• Hate speech is not allowed on the instance or in instances federated with it. This includes remarks directed at sex, gender, ethnicity, orientation, disabilities, etc…

2. Anything that relates specifically to Windows programming is welcome. e.g. native Windows development (such as WinUI, UWP, etc.), a MAUI issue which only happens on Windows, Windows Store related issues, etc.
3. When posting, bear in mind that these are also going out to people’s Mastodon feeds. i.e. try not to be overly wordy.
4. I reserve the right to modify these rules :-) (but also feel free to make appropriate suggestions for such modifications).