3 ms·

Yeah, Standard is the intersection of the 3 APIs that MS says will work no matter which you target, without needing BCLs. Core is a bit different, but not that

Yeah, Standard is the intersection of the 3 APIs that MS says will work no matter which you target, without needing BCLs. Core is a bit different, but not that different from Framework API-wise, and it will run anywhere, but has no native UI support. Framework is the original blend, and it is probably going to be mostly used for desktop applications and games going forward. Core is the future, they tore a ton of the old, obsolete features out, but it means that porting a codebase that relies on those is non-trivial. Significantly, it doesn't support Web Forms, which is great for developers but a hard sell for managers.

lloydjatkinson 9y ago
> without needing BCLs. Nope, that doesn't even make sense. The BCL is where all the base classes live. > Significantly, it doesn't support Web Forms, which is great for developers but a hard sell for managers. I can't tell if you're trolling or are serious, if you are serious that's pretty sad. WebForms is an abomination. Just because you can use drag and drop controls and "magically" get AJAX working in the background does not mean it's a good thing. I don't even know where the "great for developers but a hard sell for managers" comes from. If by your own admission it's so great, why is it not the other way around with developers hating it and managers pushing for it? Either way, that scenario doesn't happen. WebForms has for literally years been as dead as the dodo, with only 1) legacy applications using it or 2) developers who don't have a clue and haven't bothered trying to learn anything modern. ASP.NET MVC or ASP.NET Web API with a TS/JS frontend are the only 2 options you have.
jug 9y ago
So I went to their API docs and for example Microsoft.Win32.Registry is part of ".NET Core 2.0" but not ".NET Standard 2.0". I'm not sure what to make of this. It leds me to believe they have an emulation of the Windows Registry for non-Windows targets using .NET Core 2.0 as there is no warning this lacks non-Windows implementations. After all, .NET Core 2.0 is a physical, cross platform product. But is that really the case? Or will I suddenly run into some e.g. NotSupportedException?

lloydjatkinson 9y ago

> without needing BCLs. Nope, that doesn't even make sense. The BCL is where all the base classes live. > Significantly, it doesn't support Web Forms, which is great for developers but a hard sell for managers. I can't tell if you're trolling or are serious, if you are serious that's pretty sad. WebForms is an abomination. Just because you can use drag and drop controls and "magically" get AJAX working in the background does not mean it's a good thing. I don't even know where the "great for developers but a hard sell for managers" comes from. If by your own admission it's so great, why is it not the other way around with developers hating it and managers pushing for it? Either way, that scenario doesn't happen. WebForms has for literally years been as dead as the dodo, with only 1) legacy applications using it or 2) developers who don't have a clue and haven't bothered trying to learn anything modern. ASP.NET MVC or ASP.NET Web API with a TS/JS frontend are the only 2 options you have.

jug 9y ago

So I went to their API docs and for example Microsoft.Win32.Registry is part of ".NET Core 2.0" but not ".NET Standard 2.0". I'm not sure what to make of this. It leds me to believe they have an emulation of the Windows Registry for non-Windows targets using .NET Core 2.0 as there is no warning this lacks non-Windows implementations. After all, .NET Core 2.0 is a physical, cross platform product. But is that really the case? Or will I suddenly run into some e.g. NotSupportedException?