.NET Standard - Under the Hood

In this episode, we're taking a look at how they different pieces of .NET Standard allow you to reference assemblies across various .NET platforms.

[seancpp]

I love the way this architecture works. It's like one big Strategy Pattern. .net Standard is a .NET interface which can be implemented by any .NET platform

[UsmanUrRehmanAhmed]

The Type Forwarding bit to resolve dependencies both ways is ingenious. I wonder why it wasn't thought of before.

[David-idjw]

Noticing problems that don't match up with the suggested ease of use you describe.

WPF project (4.6) references Standard 1.3 library. It will build, but will crash on run because of versioning conflicts between 1.3 and 4.6, even though 4.6 is an implementation of 1.3. Solution requires adding an explicit reference to the NetStandard.Library in the WPF project, which in turn adds about 20 new DLLs to the build output, despite not being needed in the 1.3 library, and knowing that adding a reference to a 1.3 library is legit from the WPF project as long as it's version 4.6 or higher.

Also still trying to work out why a NuGet package referenced in the 1.3 library doesn't get copied to the output directory on build, which is a separate runtime failure.

[nemanja.djordjevic]

Slide named "What can you reference from .Net Standard" shows that .Net Framework, .Net Core and Xamarin can only reference My Standard Library 2.x. Why only 2.x, what about 1.x?

[sriniv]

Type forwarding made possible; .net framework project can reference a .net core library and vice versa!!!

[kieranhayes]

Great video, simple and to the point.