AvaloniaAppDelegate<TApp>.FinishedLaunching is not virtual - cannot initialize Maui.Essentials about avalonia HOT 5 CLOSED

@gentledepp in case you think docs should be imporved, contributions to the docs are welcome.

from avalonia.

Is that really needed? Related:

• #12621
• https://github.com/AvaloniaUI/Avalonia.Essentials

from avalonia.

@timunie I do not understand the question.
regarding: Avalonia.Essentials is "archived" - so not futureproof at all, right?
regarding: #12621 - they are merely discussing if it is needed or not.

Do we need Maui Essentials: Definitive "YES" since avalonia ui lacks most of the platform APIs it provides.
Do we need a documentation: Definitive "YES" since not every dev is as experienced/tortured as I am and manages to dig through open source code all day just to get things done. 😅

from avalonia.

https://learn.microsoft.com/en-us/dotnet/api/foundation.exportattribute?view=xamarin-ios-sdk-12

[Export("application:didFinishLaunchingWithOptions:")]
public bool FinishedLaunching(UIApplication application, NSDictionary launchOptions)
{
     base.FinishedLaunching(application, launchOptions);
}

from avalonia.

Also, come on, this project already handles initialization - https://github.com/AvaloniaUI/AvaloniaMauiHybrid
It was mentioned in these discussions and avalonia.essentials.

Do we need Maui Essentials: Definitive "YES"

Probably, no, since you can access platform specific APIs directly from platform projects. I.e. "net8.0-ios" projects gives you access to iOS APIs. That's a .NET feature, available with any GUI framework. But there is nothing wrong with using Essentials too, if you only need limited platforms they support.

from avalonia.