2 ms·
The main issue is that there is currently .NET Core (used mostly by web applications) and .NET Framework (used mostly by Windows applications), and many things
by ocdtrekkie 9y ago
The main issue is that there is currently .NET Core (used mostly by web applications) and .NET Framework (used mostly by Windows applications), and many things that can be done in both have to be done in slightly different ways. Sometimes I'll look up how to do something in .NET, and find a reference that doesn't work in my app... because it's only there in Core, for example. .NET Standard was the first big step, I think, in starting to clean this up: Making a clear measure of what you could expect to be common to all flavors of .NET.
The goal here, I think, is to inevitably ensure regardless of platform you're targeting or format your application is used in, it can rely on the same .NET as every other.
Whereas .NET Framework was a Windows-based design where the OS was an assumption, .NET Core is moving to add Windows-specific capabilities as an add-on.
- euyyn 9y agoThe fact that something called Core wasn't the part that's common to all flavors is a big sin.
- pjmlp 9y agoYep, that is a side effect of rebuild the world with UWP and what ASP.NET team was doing (.NET Core 1.0) before acknowledging that it wasn't actually flying, now it is taking them a couple of years to steer the ship back on track, while trying to gain the confidence of developers with 15 years of development investment in .NET Framework.