This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(185.6, 89%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ED%3C/text%3E%3C/svg%3E)
I wanted to know the difference between the NETStandard.Library package and the Microsoft.NETCore.App package. I tried to look up documentation but it's all very broad or they sound very similar saying both packages are a set of .NET API's. Is there a difference in the runtimes they can operate on (like Microsoft.NETCore.App is compatible with .netcore but not .netstandard)?
Microsoft Technologies based on the .NET software framework. Miscellaneous topics that do not fit into specific categories.
An object-oriented and type-safe programming language that has its roots in the C family of languages and includes support for component-oriented programming.
Microsoft.NETCore.App is the actual implementation of .NET Core runtime, and NETStandard.Library is the actual implementation of .NET Standard.
Their relationship has been fully documented by Microsoft in multiple locations, such as
hi @displayname
basically,
Microsoft.NETCore.App metapackage contains the .NET Core runtime and supporting managed libraries.
Note that this metapackage has a reference to NETStandard.Library, and contains all other packages required to run a .NET Core app.
NETStandard.Library metapackage references a set of packages that define the .NET Standard library.
".NET Standard is a formal specification of .NET APIs that are available on multiple .NET implementations. The motivation behind .NET Standard was to establish greater uniformity in the .NET ecosystem.", Used ofter as class library compatible with .NETCore .NETFramework and Xamarin
