3 ms·
On the topic of WPF apps in .NET core: Can anyone who has successfully migrated WPF apps to .NET core, in production, chime in on what was the experience like?
by DoingIsLearning 5y ago
On the topic of WPF apps in .NET core:
Can anyone who has successfully migrated WPF apps to .NET core, in production, chime in on what was the experience like? Any major pitfalls or pros/cons to consider?
I have a prospective client, running a WPF app in a soon to be deprecated windows embedded machine. They have a lot of domain knowledge in the app so are unwilling to re-write or port.
I was thinking if it is feasible at all to migrate this WPF app to .NET core and then migrating the target to a higher longevity Linux machine.
- notanaverageman 5y agoWPF is still Windows only. It will not work on a Linux machine.
- DoingIsLearning 5y agoIndees it seems to be a dead end. https://github.com/dotnet/wpf/issues/48 https://github.com/dotnet/wpf/issues/48 Thanks for clarifying.
- ygra 5y agoFor a WPF-like development experience that's also cross-platform, perhaps take a look at Avalonia: http://avaloniaui.net/ http://avaloniaui.net/. It's not a drop-in replacement, but very, very similar.
- Foomf 5y agoOne of the pitfalls I've encountered is the need to use the tray icon api, which as of now still is not in .NET core.
- bobcostas55 5y agoSome minor stuff with dispatching to the UI thread, nothing serious. Oh and you'll need a new package to get the System.Windows.Interactivity stuff.
- ComputerGuru 5y agoThe resulting binaries are huge if you publish self-contained. If you don’t, you’ll need to include the redistributable installer so it’s still huge. Tree shaking is still in its primacy.