ASP. NET Core 2.0: 1. Overview, asp. netcore

ASP. NET Core 2.0: 1. Overview, asp. netcore
Why ASP. NET Core?

. NET Core was a bit itchy when it was just released. I probably did not dare to put it into action. Now 2.0 has been released for a while, the previous concerns about its "instability" have also been dispelled,

I decided to study it practically.

 

As to why core is used, the official saying is:

ASP. NET Core is a re-designed ASP. NET, which changes the architecture and forms a simpler modular framework.

ASP. NET Core has the following advantages:

• Generate a unified scenario of Web UI and Web API.
• Integrates the new client framework and development workflow.
• Environment-based cloud ready Configuration System.
• Built-in dependency injection.
• Lightweight, high-performance, modular HTTP request pipeline.
• It can be hosted on IIS, Nginx, Apache, Docker, or in its own processes.
• When setting the target to. NET Core, you can use parallel application version control.
• Simplified New Web development tools.
• It can be generated and run in Windows, macOS, and Linux.
• Open source code and community-centric.

ASP. NET Core is provided as part of the NuGet package. In this way, you can optimize the application to include only the required NuGet package.

To sum up, the main attraction is cross-platform and high-performance.

 

How does one perform cross-platform operations?

Let's take a look at the general structure of. NET Framework and Core.

 

. NET Framework is a "cross-Windows" platform. On this basis, it also supports "cross-language" in C # and VB languages ",

All these languages comply with CLS and are compiled to execute. From the perspective of multi-layer architecture design, it is quite feasible to change the bottom layer.

 

. NET Core retries a CoreCLR runtime and a BCL called CoreFX. Here, ASP. NET Core is completely provided as part of the NuGet package.

In this way, the application can be optimized to only include the required NuGet package, so that the application is more flexible and modular while improving performance.

It may be a bit inappropriate to put. NET Standard here. NET Standard is not included in. NET Core, it is a set of API specifications,

. NET Core is compatible with. NET Framework by implementing. NET Standard.

 

As for cross-platform, because 90% of CoreFX code is irrelevant to the platform, such

We can rest assured that all this is "cross-platform.