Summary
- .NET Framework attempts at cross-platform in the past decade.
- To achieve cross-platform .NET Core What's the difference?
- Based on how .NET Standard platform compatibility is achieved?
Instructors
History shackles
.NET Framework = FCL + CLR
"Cross-platform" .NET Framework
Completely independent, fragmented
Reuse of War
Due to completely independent, fragmented, leading to reuse difficult, here are two solutions
Source code reuse
Assembly multiplexing
One problem: inconsistency Assembly
Resolved by Retargetable Assembly
Question two: Cross-set type transfer program
Resolved by the type of transfer mechanism (type transfer occurs when told by dll run)
The new layout
.NET Core Hierarchy
Unified .NET
.NET Standard
Why .NET Standard able to do cross-platform applications
.NET Standard assembly is a defined API, but is not achieved, the sole purpose of the type defined in the application can be automatically transferred to the corresponding platform dll, using the mechanisms of War multiplexing spoken.
Type transfer Demo
Looking to the future
Video Links
When we talk about .NET Core cross-platform, we were talking about?
related articles
Construction of a detectable with high availability ASP.NET Core Services - Study Notes
ASP.NET Core Based K8S micro electric service providers practice case - study notes
This work is Creative Commons Attribution - NonCommercial - ShareAlike 4.0 International License Agreement for licensing.
Welcome to reprint, use, repost, but be sure to keep the article signed by Zheng Ziming (containing links: http://www.cnblogs.com/MingsonZheng/), shall not be used for commercial purposes, be sure to publish the same work based on the paper license modification .
If you have any questions, please contact me ([email protected]).