Using AOT Native gives System.PlatformNotSupportedException

[atomsk-0]

When building project with AOT it gives System.PlatformNotSupportedException

• Platform: Desktop
• Framework Version: .NET 7.0.0-RC2
• API: OpenGL
• API Version: (Not sure which version im using the Silk.NET.OpenGL.Extensions.ImGui example

1. Builded project with AOT enabled x64
2. Runned it

Not sure if this is bug or silk just dont have support to aot yet.

[Beyley]

Can you give a full stack trace?

[atomsk-0]

Sure
Unhandled Exception: System.PlatformNotSupportedException: Couldn't find a suitable window platform. (none registered) https://dotnet.github.io/Silk.NET/docs/hlu/troubleshooting.html at Silk.NET.Windowing.Window.Create(WindowOptions) + 0x19d at Plutonium.Rendering.TestWindow.Run() + 0x90 at Plutonium!<BaseAddress>+0x1c4b83

[Beyley]

Ah it's that problem, you need to run RegisterPlatform on SdlWindowing, SdlInput, GlfwWindowing, GlfwInput

[atomsk-0]

Oh okay thanks that solved it.

[BTOdell]

Is there a way for Silk.NET to handle this automatically? Ideally, the application code shouldn't need to be different when publishing to AOT vs normal.

[Perksey]

Applications don't need to be different between AOT vs normal, however applications do need to be compatible with AOT. Adding the following lines

if (OperatingSystem.IsAndroid() || OperatingSystem.IsIOS())
{
    SdlWindowing.Use();
    SdlInput.Use();
}
else
{
    GlfwWindowing.Use();
    GlfwInput.Use();
}

is enough to make your applications fully AOT compliant. This will work on both AOT and non-AOT, you can just leave the code in there so the application is the same regardless of what mode you publish in. Silk by default does something similar to the above using reflection magic which is unavailable on AOT, hence the extra effort.