R.I.P InvertedBoolConverter 2014-2026 💀

Awesome!

This is a game changer!
Thank you!

Even in my wildest dreams, that didn't exist

Awesome work

thank you, please approve like yesterday!!!
@StephaneDelcroix please could @ be used to start the c# expression within the string? More like razor (eg <Label Text="@Product.Name" />). It's so that the C# is consistent. Here, I see that single quote is used for a string. Having to learn something extra, specific to this may be difficult.

One word: This is great!¹

This is awemazing, improving Xaml DevX is the biggest thing anyone can do for MAUI. I've dreamt of days like this.

Can we have this in WPF, UWP and WinUI3 too? It is amazing.

Having async void in event handlers is generally a bad thing.
I was wondering if behind the scenes there could be the FireAndForget extension method MAUI has for this kind of situations where (if available) an ILogger is being used in case of a thrown exception, but at the same time, I feel it would be probably better to not support async/await in events so that the developer is forced to think about it.
Like to me it seems this may encourage bad practices.

This is a game-changer! This is exactly the direction .NET MAUI needs to take

Consider making it feature-complete by adding support for the OR operator too.

• {A || B} - Boolean expressions (replaces MultiBinding + AnyTrueConverter)

<Lable IsVisible={async () => {
          bool canVisible = false;
          white(true)
          {
                if(canVisible)
                {
                      canVisible = false;
                      return false;
                }
                
                 awite Task.Delay(TimeSpan.FromSecond(5));
                  canVisible = true;
                  return true;
          }
      }
}}

c# inside xmal.

@StephaneDelcroix please could @ be used to start the c# expression within the string?

We've consider using @, $ and even some emojis to indicate an expression. We choose to use {} to indicate, the XAML way, that some magic is happening somewhere, and {=... } to disambiguate in rare case of conflicts between an expression and a markup extension.

We're not creating a new language here, and keeping backward compatibility is our first priority. This is why Text="@somevalue" didn't make the cut, as there is no way to know if the user expect a string starting with @ or an evaluate an expression.

@egvijayanand This already works! Any valid C# expression is supported, including ||, &&, and any other operators.

<Label IsVisible="{A || B}" />
<Label IsVisible="{IsLoaded && ShowContent}" />

This already works!

Great to hear about it 👍.

Is there a way we can avoid this whole section?

Somehow Razor is able to do it:

@jonathanpeppers razor doesn't have to be valid xml, we like that XAML stays processable by xml tools. For more complex expression that would otherwise require a lot of escaping (quotes, <, >, &), I'm adding support for CDATA

@StephaneDelcroix please could @ be used to start the c# expression within the string?

We've consider using @, $ and even some emojis to indicate an expression. We choose to use {} to indicate, the XAML way, that some magic is happening somewhere, and {=... } to disambiguate in rare case of conflicts between an expression and a markup extension.

We're not creating a new language here, and keeping backward compatibility is our first priority. This is why Text="@somevalue" didn't make the cut, as there is no way to know if the user expect a string starting with @ or an evaluate an expression.

@StephaneDelcroix thank you for your response, your work and the addition of CDATA. With the addition of CDATA, it seems a bit too much. could everything that starts with {} be interpreted as CDATA content while "" will be as it always have been.

For instance
<Label Text={Product.Name} />
or <Label Text={"MAUI"} /> (a string is quoted)

<Label x:Name="label">
    <Label.IsVisible>{Count > 0 && Count < 100}</Label.IsVisible>
</Label>

<Button Clicked={(_, _) => label.Text = "Clicking"} />

<Label Title="{Binding Name}" /> (As XAML as always been)

This may not be valid XML
<Label Text={Name} /> I wish it can be
But this is valid

<Label>
   <Label.Text>{Name}</Label.Text>
</Label>

If everything within only {} is parsed as CDATA, the only pain point I can see is using property elements whenever we want to do c# expression

/azp run

/azp run

/azp run maui-pr-devicetests

They should sustitute &amp for and

This expression works fine for regular properties, but does not detect command properties. Is there any specific reason?

Error message: Property or indexer 'MainViewModel.IncrementCommand' cannot be assigned to -- it is read only.

It seems that it tries to assign a value to the read-only Command property. In general, command properties are intended to be read-only, featuring only a getter.

Suggest creating a discussion so that feedback can be viewed in one place.