Winforms NativeAOT

[dadavadd]

Are there any plans to optimize WinForms for NativeAOT? Or will this never happen?

[ghost]

Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Are there any plans to optimize WinForms for NativeAOT? Or will this never happen?

Author:	dadavadd
Assignees:	-
Labels:	untriaged, area-NativeAOT-coreclr
Milestone:	-

[Symbai]

Are there any plans to optimize WinForms for NativeAOT? Or will this never happen?

Wrong repo: https://github.com/dotnet/winforms/issues. And yes, its unlikely. Has been asked tons of times already. Use search function for more details. The only desktop UI framework that officially works with AOT is Avalonia, then there is https://github.com/kant2002/WinFormsComInterop which may work but its not an official solution.

[Sergio0694]

"The only desktop UI framework that officially works with AOT is Avalonia"

UWP has been using AOT (via .NET Native) for like 10 years now, if we're going to just name all of them let's not forget that too 😄

WinUI 3 is also planned to get AOT support shortly (via NativeAOT).

[danmoseley]

I’m curious whether there’s insurmountable technical reasons or it’s more about the work required.

cc @eerhardt

[elachlan]

There is a large effort happening in winforms at the moment to enable AOT/trimming.

See #4649

[merriemcgaw]

@danmoseley it's about how much work there is to make this happen. That said, we're really focusing right now on the fundamentals that will enable AOT and Trimming over the next release or two. We've got lots of folks asking for it and the team is in agreement about how important the work is for us.

I am going to close this issue, in favor of the one @elachlan linked. That's the parent issue we're using as we work through getting this enabled.