Add Windows and update to net7

[juwens]

work in progress

blocked by: AvaloniaUI/Avalonia#12782

major

• added
• update to net7
• update to a regular stable avalonia release (11.0.4)

minor

• renamed ".xaml" to ".mxaml" (see caveats)
• renamed the MauiSample to MauiSampleApp so the two projects are less ambigues.

caveats

• due to an shortcoming of avalonia, which tries to parse every xaml file, and terminates and throws an error if it fails, i needed to rename every maui xaml file. analouge to the ".axaml" for ava convention i chose ".mxaml" for maui.

[juwens]

@kekekeks i tricked the build (for the while beeing) by renaming all maui xaml files to mxaml, like you ava does with axaml.

To workaround this issue: #7 (comment)

I also needed to disable FluentTheme, because it could not be resolved.

AvaloniaMauiHybrid/MauiSampleApp/AvaloniaApp.axaml

Line 6 in 157e066

<!--<FluentTheme Mode="Light"/>-->

[juwens]

it starts, no avalonia rendering visible yet (but that is expected, cause there is no code for that yet)

[maxkatz6]

due to an shortcoming of avalonia, which tries to parse every xaml file, and terminates and throws an error if it fails

It parses xaml files only if they were added in csproj with <AvaloniaView Include=".xaml" />. You don't need these.

I also needed to disable FluentTheme, because it could not be resolved.

Add Avalonia.Themes.Fluent package

[juwens]

@maxkatz6

thx for taking a look into it.

It parses xaml files only if they were added in csproj with <AvaloniaView Include=".xaml" />. You don't need these.

I think you missed the point where i already analysed and explained that in the issue.

You can try it yourself with my PR (just reset some commits before i renamed to mxaml). In the csproj no single xaml file was added to AvaloniaView.

You can look at the the binlog analysis, the problem has two main components:

1. maui implicitly adds all xaml files to ItemGroup AdditionalFiles (this is no problem, and acceptable behavior)
2. ItemGroup AdditionalFilesare are passed to the csc and the source-generators
3. AvaloniaNameGenerator sourcegen parses all ".xaml", ".paml", "*.axaml" files in the AdditionalFiles list
4. it fails critical if the xaml file (from the AdditionalFiles ItemGroup) is a maui file

#7 (comment)

#7 (comment)

[maxkatz6]

@juwens hi! I just updated main branch to Avalonia 11 with .NET 7. Seems to work fine at least on Android.

There were some issues with Kotlin StdLib on android though.

I added workaround for your issue with AdditionalFiles by disabled Name source generator, which is optional for Avalonia (it won't generate c# properties for x:Name xaml elements). I created AvaloniaUI/Avalonia#12855 to track this issue.
Either way, it shouldn't block this PR anymore, and mxaml file format is optional now.

[juwens]

@maxkatz6 thanks, i'm very grateful for your help. That'll definitely help.

Cause i try to add maui-windows (WinUI), i discovered an impediment (the lack of a WinUI "AvaloniaView"). Currently i'm digging into the whole platform-abstraction of avalonia and try to implement an AvaloniaView for WinUI AvaloniaUI/Avalonia#12782

[cesarchefinho]

@maxkatz6 thanks, i'm very grateful for your help. That'll definitely help.

Cause i try to add maui-windows (WinUI), i discovered an impediment (the lack of a WinUI "AvaloniaView"). Currently i'm digging into the whole platform-abstraction of avalonia and try to implement an AvaloniaView for WinUI AvaloniaUI/Avalonia#12782

if you can add windows and browser without maui, in the same solution as maui hybrid , then we can implement specific code in windows project or in browser project and dont use maui in these plataforms...

see #12

[juwens]

I close it for now, as there are several outstanding things to be solved before continuing here.
But i'll try to do a second attempt when i can.