Earlier quoted context omitted.
Again, I know you know this stuff - you were involved in the discussion when it was posted here. As mentioned, I spent the last 5 years doing Forms/WPF/UWP, and there is plenty of work there. There were also jobs for Windows CE developers in 2015 after MS abandoned it in 2007, would that have been a good career move? Microsoft said that they are only focusing on compatibility with Windows for .Net framework going for…
.NET Core is yet to be embraced by most enterprises, everyone is waiting for .NET 5 to actually make the switch. Too much software is now making the transition into .NET Framework 7.x, to bother with half baked support from Core to many APIs like EF6, WCF and components from third party vendors. From where I am standing, we don't care what Microsoft calls it this month, it is .NET.
Today more Linux VMs are being hosted by Azure than Windows. Microsoft is making serious investments in cross platform development and making Linux a first class development environment on Windows with improvements in WSL.
EF6 and WCF is legacy. Really? Are we arguing about SOAP in 2019?
It’s not about what Microsoft is “calling it”. It’s about where all of the future emphasis of .Net improvements are.