Ambiguous reference between 'Microsoft.MobileBlazorBindings.Elements.XXX' and 'Xamarin.Forms.XXX' about mobileblazorbindings

[rlebowitz]

One simple work-around would be as follows:

_Imports.razor:

@using Microsoft.MobileBlazorBindings
@using Microsoft.MobileBlazorBindings.Elements
@using XF = Xamarin.Forms

Counter.razor:

<Frame CornerRadius="10" BackgroundColor="XF.Color.LightBlue">
    <StackLayout Orientation="XF.StackOrientation.Horizontal" HorizontalOptions="XF.LayoutOptions.Center">
        <Button Text="Increment" OnClick="@IncrementCount"></Button>
        <Label Text="@("The button was clicked " + Count + " times")"
               FontAttributes="XF.FontAttributes.Bold"
               VerticalTextAlignment="XF.TextAlignment.Center">
        </Label>
    </StackLayout>
</Frame>

Counter.cs:

    public partial class Counter
    {
        private int Count { get; set; }

        private void IncrementCount()
        {
            Count++;
        }
    }

Note that I chose to separate the @code{} portion of the XAML file out to a separate partial class in order to retain separation of the UI and logic. You don't have to do this, but it's a practice I try to follow.

[Eilon]

Thank you for reporting this. This is unfortunately a known issue right now and I am investigating good workarounds or solutions. As you noted, these errors are indeed harmless, but I agree they are very annoying.

[Eilon]

I do have an update, finally! This appears to be a Razor Tooling bug, so I talked to @NTaylorMullen on that team about it and he worked with me to figure out the cause, so I logged this issue: https://github.com/dotnet/aspnetcore/issues/26647

I'll see if I can send them a PR to fix it but it looks like the issue might be there to help avoid another issue, so we have to figure out how to fix this without causing a regression to another important scenario.

[nickkfwong]

Since there are many attributes that goes into Xaramin.Form namespace, for now I used the full namespace for the element instead.

ie.

<Microsoft.MobileBlazorBindings.Elements.Frame>
</Microsoft.MobileBlazorBindings.Elements.Frame>

But intellisense seems doesnt work well on this though (maybe some of my config not setting correctly? - Im using VS2019 community)

[Eilon]

I'll ask some Blazor experts about this.

[whann0205]

Any news regarding this topic, since it is still present?