Predict the value of your house using Azure Machine Learning
Description
I had the privilege of joining Immo in his natural habitat to get all of the details behind the new .NET Standard Library, the one library to rule them all. What does it do? How does it work? Why should I care? Tune in!
Links:
Share
Download
More episodes in this series
Joel Spolsky Talks About Building Stack Overflow and Values Developers Care About
Related episodes
All About Visual Studio 2017
DotNetCurry: Free .NET Magazines by Microsoft MVPs
Rowan Miller - Entity Framework Core 1.1
Azure IoT TypeEdge : a strongly-typed development experience for Azure IoT Edge
F# Tooling Updates for Visual Studio 2017
What's new in F# 4.5
A History of .NET
Reactive Extensions for .NET Developers
Humanitarian Toolbox with Bill Wagner
Deploying .NET Web Apps to Azure
The Discussion
-
raghurana That's a great intro. Thanks Seth. I've started using .net standard in my Xamarin projects, but still don't fully understand what "Microsoft.NETCore.Portable.Compatibility" and "NETStandard.Library" are. Any videos explaining these would be much appreciated.
-
steven Am I understanding this right, an Xamarin App will run on windows ( with any needed windows renderers ) on the basis that Xamarin API's are inside .net standard?
-
terrajobst 14 hours ago, raghurana wrote
I don't fully understand what "Microsoft.NETCore.Portable.Compatibility" and "NETStandard.Library" are.
Microsoft.NETCore.Portable.Compatibility is a NuGet package that provides the magic that makes your project compatible with existing Portable Class Libraries (PCL). PCLs were our solution to create class libraries that can be shared across multiple .NET flavors, prior to .NET Standard.NETStandard.Library that's the NuGet package that you reference to build a class library targeting .NET Standard 1.x.
-
terrajobst Am I understanding this right, an Xamarin App will run on windows ( with any needed windows renderers ) on the basis that Xamarin API's are inside .net standard?
No. Xamarin provides .NET flavors that allow you to run apps on iOS and Android. We don't have any plans to add a UI stack to .NET Standard. UI is a platform specific technology.Xamarin Forms is an abstraction over the platform specific UI stacks that allows you to share UIs across different operating systems.
-
Code So for ease of understanding, is it OK to think of .NET Standard as the spec and .NET Core as one of it's implementation?
Also, there seems to be some difference as to how .NET Core is represented in terms of architecture - does the Standard replace the Core's place in the first diagram in this link?
https://blogs.msdn.microsoft.com/bethmassi/2015/02/25/understanding-net-2015/ -
danny How it differs from BCL/CLS
-
JTCH So is it correct to say .net core is a subset of .net framework? They seem to be parallel to each other.