It looks like WPF will be supported for the forseeable future, but I get your overall point
I think the netstandard -> all platforms approach, combined with the aggressive depreciation of old .Net 4.6.x versions is a road map for the future.
Maintaining two entire release chains, the 4.x and the .Net core 2.x, is an impossible long term strategy.
I would be absolutely astonished if the 4.x line is quietly folded away and depreciated ('unsupported') once the netstandard surface area means the code bases that no longer run on the .Net core fall to significantly small fraction.
At that point there will just be 'one' .Net again, and it will be .Net core, on all platforms.
Significantly, there seems little to no indication (https://github.com/dotnet/core/issues/43) that winforms and WPF are going to .Net core.
You might argue that Microsoft is a legacy beast, and they won't abandon their developers by dropping support for old versions, but they already are doing that in the 'you can install it, sure, but it'll never get any more updates' (#1, #2), so you know.
Don't bet the farm on a WPF app. Just saying.
#1: https://blogs.msdn.microsoft.com/dotnet/2015/12/09/support-e...
#2: https://support.microsoft.com/en-us/help/17455/lifecycle-faq...
Not sure about WPF. It's a shame because it's a great development experience.
Generally, having something cross-platform either means you're terrible everywhere (Swing), terrible on non-primary platforms (GTK), or have to invest a lot of work in making things work well and still don't quite feel native (Qt). Or you go the Xamarin Forms route and have a few core controls that have to be implemented natively on every platform, which reduces their features to the lowest common denominator, often doesn't expose or enable low-level platform details that may sometimes be needed for customization, and means that you have to invest thrice as much effort into making everything work.
In my experience UI frameworks either are bound to a specific platform, or suck. Or both. But a cross-platform WPF would be awesome, but I'd rather expect UWP to become cross-platform instead of WPF.
[1] https://en.wikipedia.org/wiki/XVT
[2] https://en.wikipedia.org/wiki/Advanced_Message_Queuing_Proto...
I've seen them promote at least 2 different technologies since the first time I heard WPF was dying, and both of them are dead already, so far as I can tell.
Yeah, I don't think winform / wpf is going anywhere quite yet.
At .NET Conf 2017 they announced support for macOS, Linux and WPF. And demoed macOS and Linux current status.
While previously at BUILD 2017 they announced XAML Standard for interoperability between WPF, UWP and Xamarin.Forms.
Which kind of implies it is the way forward.