.NET Standard - Introduction

I'll show you what .NET Standard is and why should care about it.

[ferrydeboer]

Best explanation I've seen so far!

[Melonno]

Great explanation what idea is behind .Net Standard. Thanks!

[emascheg]

Great video, Thanks
Better understanding about .NET Standard

[fredimachadonet]

Hi Immo! Awesome video, extremely useful. I look forward to watch the next videos. Thank you!

[ReuelRamos]

What's blows me away is:
.NET Standard, even though wasn't introducing breaking changes, it jumped straight to 2.0 given the tons of changes it had.
Fair enough.

But .NET Framework 4.6, which implemented .NET Standard 1.3, released a MINOR version 4.6.1 targeting 2.0!
WHAT?

[StephenRayner]

Haha Immo you are hilarious. Thank you and your team for all the hard work for .Net Core and .Net Standard. PhD in Venn diagrams lol!

[sushil]

What's the basic difference between .NET implementation and .NET platform?

[abuyoyo]

Immo - can you please explain the 'Windows' line on the version table? Did windows 8/ 8.1 contain .net implementations by themselves, that were dropped in 10.0? Is it another matter altogether?
Thanks for all the great videos!

[marcosbeni]

5:20 Isn't that going to cause the .NET Standard Specification to over time start getting bloated with lots of potentially obsolete APIs from older versions of the standard?
Doesn't it make sense to also include a "Minimum Compatibility Version" in the .NET Standard Specification so that Microsoft is able to drop obsolete APIs in newer versions of the standard?
For example, .NET Standard 10.0 might have a "Minimum Compatibility Version" with .NET Standard 2.0, which tells you that .NET Standard versions bellow 2.0 have obsolete APIs not included in .NET Standard 10.0. Any libraries targeting versions below 2.0 have to upgrade to at least 2.0 to be able to work on newer versions of the standard.
Of course, APIs would have to be marked as "obsolete" first to encourage libraries to stop using them, and then actually drop them much later in the future, giving developers enough time to prepare.

[navanitamukherji]

So if I create a dll using target .net standard 2.0, which .net framework will I need on my computer to be able to run it? Can it be either .net framework or .net core framework? I am integrating the dll created to an automation tool.

[richardpawlak]

Hard to understand. A lot of noise/echo/reverb.

[reyou]

How far that version support schema will expand? Seems to me vertical scaling instead of horizontal. I am a .Net lover by the way, but wanna make sure not to miss something :)

[AzazeoAinamart]

Great video, thank you.
I have a question about API deprecation policy - is it defined? (asked also on Github issues)

[Naster]

Hi Immo, could you confirm that UWP will support Net standard 2.0? Thx!

[Ironboost]

So I guess this is why I can't make a new PCL cross-platform project anymore... well, if it's for the better, then I'm in

[mduckernz]

Oh man, such a missed opportunity! Star Wars movie posters instead of The Lord of the Rings posters!

One standard to bring them all and in the API bind them...

[AbdulQadirKhan]

what circles has he said ? at [05:32] - [05:33] ? Consubject circles ?

[pgtips]

Just near the start you showed a visual snapshot of the different BCLs that exist and then you showed another image showing .Net Standard as having ALL BCLs. This is not technically true and is one of the reasons why so many people are confused. The .Net Standard is not a BCL, it's just a standard.
What also is missing in order to fully grasp .Net Standard is a look and explanation of the empty classes, what they actually function as and how visual studio uses .Net Standard to guide a developer. All this and more need to be accurately explained in order to get a satisfactory understanding of the what, why's and hows of .Net Standard.

[jamesallen]

THANK YOU for removing those arrows on the github version page. That was an awful design idea. I read the table as .net framework 4.6 being good for .Net Std 1.4, 1.5, and 1.6.