Open kant2002 opened 2 years ago
@kant2002 Does this mean there is progress in wpf support?
@unofficialdev I did not forget about WPF. I refresh what I have to run on WPF7 and discover that I have to rewrite at least DirectWriteForwarder
. That was expected, but my hopes was, that I can at least somehow show empty form.
This requires me to go all-in. That's risky and nothing which I can do in small incremental steps.
I'm looking for options how I can pay risks in smaller pieces. If I would not find a way, I will try to go all-in and check what happens.
If you know community of developers who willing to at least test experiement, or company who willing to probe the water, I can take more risky stance on the matter.
Does it really benefit WPF apps?
Do people really need that?
compiling with Native AOT can give WPF resistance to decompile IL code. a problem that a lot of developers want. unfortunately I can't afford to contribute :(
https://github.com/dotnet/wpf/issues/5305#issuecomment-1148621250
With custom WPF build I think people can start playing with NativeAOT and WPF
You did the impossible Mr. @kant2002 , thank you! 👏 🥳 Do you believe this will eventually go to the official channel release anytime in the future?
I would say, this questions better ask in WPF repo. First things is to make sure that WPF accepts community contribution on more faster cadence. If you want this, please go to WPF repo and express your request there. Team should know that people want WPF to be community driven,
wpf support for native AOT would be very useful for my company, I'm developing several tools in avalonia because wpf is not supported
So far with .NET 7 I can list following issues
Output form ILC. CoClass usage should be replaced with ComWrappers
DirectWriteForwarder
crash in main. That is blocker