The Right Way to Conditional Render in .NET MAUI 

I forgot to mention that the performance part of this video was heavily inspired by this blog post by XamGirl! xamgirl.com/stop-doing-isvisibletrue-false-to-show-hide-views-in-runtime-in-xamarin-forms

Thanks. This works great. Performance has improved. I called by class RenderThis instead of If. If you think someone out there has introduced a better way of doing this since you posted this video, please do let us know.

Your WPF tutorials are like treasure ! Can you please make a tutorial about right way to do localization in WPF ? Thanks for the amazing content.

This is great. I managed to implement it with the mvvm pattern (using the community toolkit) by binding the condition to a boolean property on the viewmodel which I set on page load. Works perfectly. Thanks again!

The most best explanation of "Bindable Property".

Hi, I am really appreciate you delivery this content to solve what's the dependant property is since this problem prevents me away from any xaml app.

This is amazing, I never knew about this issue and Im actually facing it, I have two CollectionViews and Im showing only one of them but in terms of performance Im sure this will be an issue. but with your solution its gonna avoid that. Thank you bro and I hope to see more MAUI Content.

hey random question could this be extrapolated to a three way validation i.e., if condition == 1 => display view1 else if condition == 2 => display view2 else => display view3 btw great video I can see this becoming a game changer in the MAUI community

Really nice solution and explanation.

Could this be done with an enum value like a switch?

You're conflating terminology somewhat: the label isn't being rendered. The problem comes from it still being in the logical tree and thus loaded like other controls (as stated with the listview example)

Good video but should it be this hard to do something like this?

Does the same approach work in WPF?

You know you are working in a ui framework when you need mountains of boiler plate to accomplish basic functionality… still nice solution.

4:38 If class is not ambiguous between if condition?

Very nice

That's way too much code and logic in your xaml. Your xaml should be lightweight. How bloated would this be if you have hundred fields. You can't reuse this as well in other forms without copying large chunks of mess.