Unveil the mystery of the .Net ecosystem in an easy-to-understand way!

When it comes to .Net, the first reaction for most people is probably the .Net Framework and Visual Studio. The first version of the .Net Framework was released on February 13, 2002. This is almost an era of prehistoric civilization in the era of rapid technological advancement.

After the release of the .Net Framework, Microsoft has been working to make it a usability development platform for the modern Web, mobile and cloud era. This has also led to the development of .Net Core 2 and .Net Standard 2.0, but this rapid development has often confusing people into the huge .Net ecosystem.

We all know the .Net framework, but how does it work in the base class library? What is a portable library? When is it used? What is .Net Core? What is the difference with the .Net Framework? What is .Net Standard? how to install? How to create a reusable library?

All of the above factors can cause problems when you choose a project. What is the .NET standard class library, .NET Core or .NET Framework? What are shared projects and portable libraries? Where should you concentrate? Should I learn everything and give up old knowledge? How to choose runTIme? ... These are the key issues that need to be understood before starting the next project or learning new technologies, so this article will try to answer these questions in the text.

.NET ecosystem explanation

In order to meet the needs of modern applications, the .Net ecosystem is undergoing continuous upgrades. The following picture shows the current state of the .Net ecosystem:

.NET Framework

The oldest and most deadly runTIme in the .NET ecosystem is the .Net Framework. This is also a place that everyone can easily confuse. Many people think that the Net Framework naturally thinks that this is a framework. Of course, it is a framework, but it is also a platform. All runTImes are like this.

As mentioned earlier, the .Net Framework has been very eye-catching since its inception in 2002, and users can use it to build WPF, Windows Forms, ASP.NET Forms, and MVC applications.

The .Net Framework can build multiple types of applications, but is primarily Windows-centric. This is because the .NET Framework uses some Windows-specific APIs for certain application types.

.NET Core

.NET Core was released in 2016 and can be used to create ASP.NET Core and Universal Windows Platform (UWP) applications. Support for cross-checking and concurrent configurations means that multiple versions of .NET Core can be run on the same computer, which is small and performs well.

.NET Core is not a new version of the .NET Framework, it is just a different version that can be used for some use cases. .NET Core does not replace the .NET Framework.

Momo for Xamarin

Momo runTIme itself is also a cross-platform implementation of the .Net Framework that can run a variety of applications, such as consoles and Windows Forms applications. Because this article focuses on the .NET ecosystem, Mono's discussion will focus on Xamarin.

Xamarin has been running since 2011 to create apps for iOS, MacOS and Android. It can build and run native or near-native applications through a mobile platform. Xamarin's Mono runtime can build Xamarin.Mac applications using specific APIs for iOS and Android.

.NET Standard

The above three runtimes all implement .Net Standard. .NET Standard is a specification for the .NET API that provides an implementation for each .NET runtime. Therefore, the code created for this runtime can also be executed by another runtime.

Tools and infrastructure

All runtimes require tools and infrastructure to compile and run the code, including familiar languages ​​such as C#, VB.NET, and F# that run in the runtime. Build tools include MSBuild, Common Language Runtime (CLR), and CoreCLR.

Runtime comparison

Let's compare the differences between the three runtimes, such as workload, installation, usage, and so on.

in conclusion

Everything mentioned in this article can be called the .NET development platform.

The .NET Framework, .NET Core, and Mono are runtimes, which also contain libraries and frameworks for building applications.

The .NET Standard Library is a set of API specifications that are not what users download and install, but rather a specification that describes what the API and API do.

Finally, infrastructure means that all of the above works, it includes compilers, languages, and runtime components such as garbage collectors and just-in-time compilation.

The .Net ecosystem looks complicated, but when you break them down like this, you'll discover how Microsoft is transforming its ecosystem and keeping it alive and vital.

Film Temperature Measurement Thermistor

Film Temperature Measurement Thermistor

Film temperature measurement NTC Thermistor is small and light as to be convenient to mounting. With the characteristics of high stability and reliability, superior electrical insulation and fast response, this type of thermistor can be used in household appliance, computer and printer etc.

Film Temperature Measurement Thermistor,Computer Sensors,Cpu Thermometer,Cpu Temp Monitor

Feyvan Electronics Technology Co., Ltd. , https://www.fv-cable-assembly.com