If you want to release a .NET MAUI app on macOS (or even iOS), I'm going to assume you want to develop at least part time there.

Visual Studio on macOS is dying, which leaves us with either using a dying app or using VSCode (which I wish everyone would write like that... VSCode. Then it'd actually be easily googleable).

Using VSCode for .NET MAUI isn't straightforward, imo, but I found a pretty danged good tutorial on it from James Montemagno, a long-time Xamarin user and MS employee.

MAUI on VSCode lacks some stuff like XAML designers, iirc, but he actually decided to use VSCode and straight-code the UI in C# for this video, which makes it perhaps the best, "How to use MAUI on macOS" tutorial out there right now.

So here you go...

Recreating Threads App with .NET MAUI & NEW VS Code Extension!

aka "The best tutorial for coding MAUI on macOS available today".

No thanks [for me for showing you this] necessary. ;^D

A few other .NET MAUI links to remember (might edit as I add them here):

• James' MyCoffeeApp, a sort of "reference" Xamarin/.NET MAUI app.
  • Note that it has stuff like this intro to MVVM in the list at the bottom.

Labels: .NET, maui, noteToSelf, xamarin, xaml

From microsoft.com (via StackOverflow):

Requirements for a Custom Class as a XAML Element

In order to be able to be instantiated as an object element, your class must meet the following requirements:

• Your custom class must be public and support a default (parameterless) public constructor. (See following section for notes regarding structures.)

• Your custom class must not be a nested class. Nested classes and the "dot" in their general CLR usage syntax interfere with other WPF and/or XAML features such as attached properties.

[emphasis is mine]

That's got to be a joke, right? So I can't use a "nested class" (which would include anything with a java-style like com.yourCo.namespace) like this to create a ListView item template?

<ListView Grid.Row="1" Grid.RowSpan="1"
            Name="lstEps"
            IsItemClickEnabled="True">
    <ListView.ItemTemplate>


        <DataTemplate x:DataType="PodcastersFeed.Entities.EpCapsule"><!-- <<< No can haz namespace!! -->


            <Grid>
                <Border Background="LightGray" Height="30" Width="250">
                    <TextBlock
                        Text="{x:Bind Title}"
                        FontSize="18"
                        Foreground="Green"/>
                </Border>
            </Grid>
        </DataTemplate>
    </ListView.ItemTemplate>
</ListView>

Look, that's crazy-insane. I'd also had trouble with "namespaced" UserControls I'd created in the past, and lucked into figuring out they'd only work for me when I took them "out" of the non-local namespace, but figured I was doing something wrong. Maybe not.

Wow. I've made a wrapper class in my local namespace as a shuttle.

UWP unfortunately remains a hacky place.

Labels: c#, uwp, xaml