Nikita Tsukanov

You need to use R2R. Startup time is increased mostly due to JIT.

Try running `dotnet publish -r osx-x64 -o build` (or `dotnet publish -r osx-arm64 -o build`)

>library load disallowed by system policy Are you sure that you have a valid `.app` bundle and that said bundle is allowed to run?

There are plans to finish and merge https://github.com/AvaloniaUI/Avalonia/pull/6391 before 11.0. That should be way more stable.

@StipecMV that's a completely different issue. Your `glXGetProcAddress` has failed for `glXCreateContextAttribsARB`. Which Linux distro are you using?

When diagnosing renderer-related bugs, a check was added to prevent visuals from being invalidated while renderer is actively building a scene (since it's something that shouldn't happen): https://github.com/AvaloniaUI/Avalonia/blob/ce98bffe66e92b3b68205036f0fe4dfeb2b138e8/src/Avalonia.Base/Rendering/DirtyVisuals.cs#L33-L36 It seems...

https://github.com/kekekeks/Avalonia.Ide - our library for XAML completion

1) Set `Name` property on the `Application` in your `App.xaml` 2) Add a customized native app menu to your `App.xaml`: ```xml ``` it will replace the default one. We probably...

@jeffdoolittle `App` class can have it's own `DataContext` You are supposed to initialize it in `OnFrameworkInitializationCompleted`

OSX: NSPasteboardTypePNG X11: Need to add support for `image/png`, `image/bmp`, `image/x-bmp`, `image/x-MS-bmp`, `image/jpeg` TARGETS