4 ms·
Microsoft naming strikes again. I suspect they're only dropping the "core" now because they can - below 4 there's a need to disambiguate versus .net Framework v
by pjc50 5y ago
Microsoft naming strikes again. I suspect they're only dropping the "core" now because they can - below 4 there's a need to disambiguate versus .net Framework versions.
- mattmanser 5y agoAnd the road between .net core 1 > .net core 2 > .net core 3 was extremely bumpy.
- darrylb42 5y agoNot to mention there is no upgrade path from .Net Framework to Core. Major missing features like WCF are still an issue in .Net 6. Migrating is a long and slow processes. Luckily we can use .Net Standard 2.0 as a bridge for libraries.
- pjmlp 5y agoOr features like how Assembly reloading and MSIL code generation works.