Roadmap - Migration to .NET Core?

[Greif 0]

Is it on the road map to migrate the code-base to use .NET core? Taking advantage of the multi-platform benefits?

[Rick Brewster 1,522]

Nope.

 

Multi-platform runtime does not mean a multi-platform framework. WinForms will still be Windows-only, as will all of the Windows-specific code in Paint.NET.

[Rick Brewster 1,522]

BTW this has changed from a "nope" to a "maybe / hopefully / I want to", especially since the announcement of .NET Core 3 including support for WinForms and WPF. And the fact they already have Paint.NET running "in the lab" on .NET Core 3 as per Richard Lander's blog post, https://blogs.msdn.microsoft.com/dotnet/2018/05/07/net-core-3-and-support-for-windows-desktop-applications/ 

[Joshua Lamusga 229]

Readers should note that WinForms and WPF in .Net Core 3 will still be Windows-only, so updating to it won't make Paint.NET multi platform.

[Rick Brewster 1,522]

15 hours ago, Joshua Lamusga said:

Readers should note that WinForms and WPF in .Net Core 3 will still be Windows-only, so updating to it won't make Paint.NET multi platform.

 

That's correct.

[Evengard 0]

AvaloniaUI is crossplatform though, but migrating WinForms to it would be probably too hard?

[Rick Brewster 1,522]

I am not porting to Avalonia. It's not even about difficulty, per se, but the volume of work. I'm not rewriting the whole UI, especially when it works just fine and when Avalonia is still an unproven platform (even if it's maturing at a healthy pace).

 

I am not planning on going cross-platform with Paint.NET at this time. I'll definitely blog/tweet about it pretty loudly if I change my plans.