3 ms·
A few related questions: what is the biggest difference between Core 3 and Framework 4.8 in terms of APIs? Superficially the difference was desktop and a few ot
by alkonaut 9y ago
A few related questions: what is the biggest difference between Core 3 and Framework 4.8 in terms of APIs?
Superficially the difference was desktop and a few other areas. Is there a reason to keep both branches of the ecosystem if the API surface grows ever more similar?
Second: is the goal of Core 3 to be “feature complete” for the desktop APIs in the sense that existing .NET 4.7 Windows Forms apps (for example) should work without change in .NET Core 3, or is it a less ambitious plan initially?
- runfaster2000 9y agoSome apps might run completely unmodified, but that's not really our plan. We intend for folks to update their apps to target .NET Core 3. We intend to support all the APIs that we find that client apps use. We're not including ASP.NET Web Forms, for example, but we'll definitely be supporting System.Drawing. We've already shifted to putting more effort into the .NET Core project. The last few .NET Framework releases have been pretty targeted. That trend will continue. We'll continue adding existing .NET Framework APIs on Core to make it so that devs can move more and more apps to .NET Core. That's the basic plan. From the post: * Desktop applications will need to target .NET Core 3 and recompile. * Project files will need to be updated to target .NET Core 3. * Dependencies will not need to retarget and recompile. There will be additional benefits if you update dependencies.