4 ms·
The interesting thing to note is that the core runtime in netfx hasn't changed in a long while (.NET Framework 3.x and .NET Framework 4.x are still essentially
by WorldMaker 8y ago
The interesting thing to note is that the core runtime in netfx hasn't changed in a long while (.NET Framework 3.x and .NET Framework 4.x are still essentially CLR 2), and it sounds like after what Microsoft learned from the CLR 1 -> CLR 2 (.NET 1.0 -> .NET 2.0) update they never want to do that again if they can avoid it. CLR 1 to CLR 2 had a very good reason to do that (generics); .NET Standard 2.1 has a lot of little reasons, but no good, big reason to break the .NET Framework world with a runtime upgrade.
(Also, it looks like ASP.NET Core still should be considered .NET Standard 2.1 compatible, but yes the "upgrade" to .NET Standard 2.1 is fascinating because it loses compatibility with netfx.)
- oaiey 8y agoASP.NET Core is not .NET Standard based. Most of its libraries are, but the core runtime is bound to a platform like .NET Core (and earlier the .NET Framework). It was never running on a pure .NET Standard interface.
- WorldMaker 8y agoOne of the biggest reasons for that seems to be Span<T>, so it seems possible that ASP.NET Core can move toward .NET Standard 2.1, since it includes Span<T>. Certainly it isn't guaranteed, but it seems plausible. (Not that it would help much in the case that .NET Framework doesn't seem to be capable of .NET Standard 2.1.)
- int_19h 8y ago> (.NET Framework 3.x and .NET Framework 4.x are still essentially CLR 2) Not quite. There is a grand total of three different major versions of the VM on Windows: CLR 1.0 - used by .NET Framework 1.0 and 1.1 CLR 2.0 - used by .NET Framework 2.0, 3.0 and 3.5 CLR 4.0 - used by .NET Framework 4+ These can all be installed side-by-side, and any particular .NET application is bound to a particular CLR version. The differences between 4.0 and 2.0 are far more minor than the ones between 2.0 and 1.0. 2.0 added a bunch of changes visible on IL level - most notably, generics, and all the new IL opcodes and metadata to support them. 4.0 was mostly internal improvements - better JIT, GC etc. But there were also some new features, like NoPIA and "uncatchable" exception types (StackOverflowException etc), and a new CLR hosting API that allowed it to be hosted side-by-side with old frameworks in a native app.