Update to preview6

[Mrxx99]

This updates the templates to preview 6.

Browser template for C# works fine, but the F# one leads to a blank screen, not sure what's wrong there.

[maxkatz6]

Is it possible to return Task here without awaiting or blocking anything?
Blocking async calls isn't supported on WASM backend.

[Mrxx99]

Yes, a better way is needed here, will take another look later (I am not to familiar with F#) or someone with better F# knowledge can give some hint

[maxkatz6]

I don't think there is needed for better way. It just needs return a Task produced by StartBrowserAppAsync.
This code is executed by WASM interop layer, so it is expected to either return int/void or return a Task.

[Mrxx99]

but StartBrowserAppAsync does not return Task<int> and F# does need an int return of main

/AvaloniaXplatfnet70.Browser/Program.fs(20,9): error FS0193: Type constraint mismatch. The type 'Task' is not compatible with type 'int'

[Mrxx99]

Thanks to ChatGPT I found out how to do it in F#. It would be a bit nicer though if StartBrowserAppAsync would return Task<int> instead of Task

[Mrxx99]

I am also not sure which parts of this properties set here are also required for the template: https://github.com/AvaloniaUI/Avalonia/blob/master/samples/ControlCatalog.Browser/ControlCatalog.Browser.csproj

[Mrxx99]

The F# Browser problem seems to be in the dotnet.js, it breaks in the first line of it, but I don't see any error message.
Can maybe someone take a look I don't know how to solve this?

@maxkatz6 Should I maybe split the C# and F# update to 2 PRs so C# can at least already be updated while F# is investigated?

[maxkatz6]

The F# Browser problem seems to be in the dotnet.js, it breaks in the first line of it, but I don't see any error message.

As I mentioned above, WASM doesn't support sync awaitl, so operations like RunSynchronously don't make sense there.
It should be a Main method (or any other method) that returns Task. In fact, browser template doesn't really care about entry point in c#, as it's not really used as an entry point. Real entry point is in JS code. Though, F# compiler might not expect that.

"dotnet.js" can be modified to execute a different method too.

It would be a bit nicer though if StartBrowserAppAsync would return Task instead of Task

I think we can do it.

Should I maybe split the C# and F# update to 2 PRs so C# can at least already be updated while F# is investigated?

Yeah, let's do it.

[Numpsy]

fwiw, I've had the Avalonia.FuncUI web assembly control catalog app running with Avalonia 11 preview 6 by doing

    let main argv =
        task {
            do! buildAvaloniaApp().StartBrowserAppAsync("out")
        }
        |> ignore

        0

Though I don't know if this is actually the 'correct' way to do it

[Mrxx99]

@maxkatz6 I have done a new PR for C# only here: #181

I also made the proposed change from @Numpsy here, I think the way it's done is fine, as the result was also ignored before and it seems to work.

So you can decide if you first want to merge C# only or directly this one.

[Mrxx99]

Also this is not yet answered:

I am also not sure which parts of this properties set here are also required for the template: https://github.com/AvaloniaUI/Avalonia/blob/master/samples/ControlCatalog.Browser/ControlCatalog.Browser.csproj

E.g. should that <EmccFlags>-sVERBOSE -sERROR_ON_UNDEFINED_SYMBOLS=0</EmccFlags> also be set? I guess it would suppress the build warnings that currently occur. Or should these be fixed in the Avalonia repo?

[maxkatz6]

@Mrxx99 this flag is automatically set https://github.com/AvaloniaUI/Avalonia/blob/e4ed304234ee69dab7cd300afafe659869e11172/src/Browser/Avalonia.Browser/Avalonia.Browser.targets#L11