Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

What is the difference between .NET Core, Xamarin, .NET Standard and .NET Framework

2025-04-03 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Development >

Share

Shulou(Shulou.com)06/02 Report--

This article mainly introduces the differences between .NET Core, Xamarin, .NET Standard and .NET Framework. What is introduced in this article is very detailed and has a certain reference value. Interested friends must read it!

.NET Core

The .NET Core is free, cross-platform, and an open source implementation of the managed framework. It supports four types of applications: console, http://ASP.NET Core, cloud, and generic Windows platform (UWP). Windows Forms and Windows Presentation Foundation (WPF) are not included in the .NET Core.

Technically, .NET Core only supports console applications. Http://ASP.NET Core and UWP are application models built on the. NET Core

Unlike the .NET Framework, .NET Core is not considered as a Windows component. Therefore, updates are in the form of NutGet packages, not through Windows Update. Because the .NET Core runtime is installed as App-Local, and the application upgrade is done through the package manager, the application can be associated with a specific .NET Core version as well as a separate upgrade.

.NET Standard

Each implementation of the managed framework has its own set of base class libraries. The base class library (BCL) contains classes such as exception handling, strings, XML, Imax O, networks, and collections.

The .NET Standard is a specification that implements BCL. Because .NET implementations need to follow this specification, application developers don't have to worry about a different BCL for each managed framework implementation.

Framework class libraries (FCL), such as WPF, WCF, http://ASP.NET, are not included in BCL and, therefore, are not included in the .NET Standard.

The relationship between the .NET Standard and the .NET implementation is the same as that between the HTML specification and the browser. The latter is the realization of the former.

As a result,. NET Framework, Xamarin, and .NET Core, each of which implements BCL in A. NET Standard. As the computer industry continues to introduce new hardware and operating systems, a new .NET managed framework will emerge in the future. The standard lets application developers know that they can rely on a consistent set of API.

Each .NET version corresponds to a .NET Standard version.

API is consistent, making it easier to migrate applications to different managed implementations and to provide tools.

The .NET Standard is defined as a separate NuGet package because all .NET implementations must support it. The tools become easier because they have the same set of API for a particular version. You can also build a library project for multiple .NET implementations.

You can also build a .NET Standard wrapper for a specific platform API.

.net Standard vs Portable Class Library

Doesn't the portable class library do the same thing?

Portable classes use a generic API that is supported by multiple platforms. Therefore, the more platforms you support, the less API is available, and it is difficult to know which API is supported for a particular combination of platforms. For a new platform, the existing PCL must be recompiled. PCL also requires Microsoft to create a new framework implementation branch for each platform.

Because the .NET Standard identifies API rather than an implementation, there is no need to recompile the application. Any newly released .NET implementation implements the necessary libraries. Applications do not need to be recompiled to run on new hardware platforms or operating systems. In theory, it is possible to catch NotSupportedException exceptions when you call API, but that should be rare.

Summary

The .NET Standard is an API specification, and each specific version defines the base class libraries that must be implemented.

The .NET Core is a managed framework optimized for building console, cloud, ASP.NET Core, and UWP applications. Every managed implementation, such as Xamarin, .NET Core, or .NET Framework, must follow the. NET Standard implementation BCL.

The .NET Framework is used to build desktop applications and http://ASP.NET applications that run on the Internet Information Server (IIS). It is the first managed framework.

Xamarin is a framework for building iOS, Android, macOS, and desktop applications.

That's all of the article entitled "what's the difference between .NET Core, Xamarin, .NET Standard and .NET Framework?" Thank you for reading! Hope to share the content to help you, more related knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Development

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report