3 ms·
From an interface perspective. From a behavioral perspective not so much. A lot of classes will throw not implemented or have slightly different results
by oceanswave 9y ago
From an interface perspective. From a behavioral perspective not so much. A lot of classes will throw not implemented or have slightly different results
- jasallen 9y agoThat's true, but it's done so that you can have simple 'if' logic to determine if something is available without having to recompile. If the interfaces were missing altogether the libraries wouldn't be portable from one implementation to another.
- janpieterz 9y agoWait... first I've heard of this. Not that I'm reading every single post letter for letter but have been following the .NET Standard move quite a bit. Is there a list somewhere that specifies what is not implemented per target, though it's in the standard?
- snuxoll 9y agoThere's multiple releases of .Net Standard, different releases of .Net Core target different releases of Standard. .Net Core 1.2 will be the first version to support the full .Net Standard 2.0 API surface.
- mellinoe 9y agoJust to clarify, we are actually calling the next version of .NET Core "2.0" so that the name aligns with .NET Standard 2.0, and so their relationship is more clear.