2 ms·
The issues people have with the move largely revolve around applications that need .NET Framework (such as WPF applications) which embed network servers current
by mathw 9y ago
The issues people have with the move largely revolve around applications that need .NET Framework (such as WPF applications) which embed network servers currently built on ASP.NET Core 1.x, which runs happily in that scenario, but 2.0 won't and 1.x support isn't going to be around for more than a year after 2.0 drops.
WPF will probably never work on .NET Core, so after that they're going to have to have some kind of elaborate multiprocess solution if they want to stay in supported versions.
- cm2187 9y agoBut also all the third party libraries. Very few run on .net core.
- WorldMaker 9y ago.NET Core 2.0 should run most libraries from every verson of the .NET Framework 1.0 to 4.6.1 (and potentially higher), with very few exceptions (albeit in some cases literally exceptions). (That's all the work that has gone into defining the .NET Standard 2.0 API.)