Relationships between versions of. Net

NET Framework 2.0,3.0 and 3.5 Three versions are as follows:. NET Framework 2.0 = CLR 2.0 + FCL (Framework class Library). NET Framework 3.0 =. NET F Ramework 2.0 + SP1 + WPF + WCF + WF + cardspace.net Framework 3.5 =: NET Framework 3.0 + SP2 + new compiler

The three versions of the framework's CLR are all 2.0, so that the ASP. NET runtime is only 1.1 and 2.0, new features like LINQ are actually implemented with new compilers plus some new class libraries, and the 3.5 version does not have a big upgrade to the CLR.

VS2008 supports the development of projects in 2.0,3.0 and 3.5 three versions, VS2005 projects can be smoothly promoted to VS2008, VS2008 projects under VS2005, compilers and class libraries are the same as VS2005, but provide a better development environment. ----------------

Quote a Description: Understanding the relationship between. NET Core and the. NET Framework.

The

. NET Core and the. NET Framework have the A  subset-su Perset  relationship. NET core is named "Core" since it contains the Core features from the. NET framework, for both the runtime and the Framework libraries. For example,. NET Core and the. NET Framework share the GC, the JIT and types such as& nbsp String  and  List<T> . We ' ll continue improving these components for both. NET Core and. NET Framework.

. NET Core is created so that. NET could is open source, cross platform and is used in more resource-constrained Environme Nts. We have also published a subset of the. NET Reference Source under the MIT license, so, and the community can port Additional. NET Framework features to. NET Core.

Above these two paragraphs, the most important is the first two sentences, the relationship between. NET core and the. NET Framework, is "Subset-superset", can be understood as a subset of the relationship, the. NET Framework is a big concept,. NET Core It is the core part that is separated from it, Dudu before, there is a metaphor: the. NET Framework is Unix,.net Core is Linux, in fact, this metaphor is always not very appropriate, so the analogy is that. NET Core is from the. NET Framewo RK evolved, sort of like a parent-subclass relationship, rather than a subset relationship.

Answers to several questions of the park friend:

1. Does the. NET Framework 4.6 fully include. NET Core 5? In other words, code written in. NET Core 5 can be compiled directly using the. NET Framework 4.6.

--Fully include (4.6 is the. NET Framework version number, not the. NET Framework base Class library version number), the. NET Framework is a big concept, and compilation is the work of the compiler, and of course the concept contains compilers, which can be said to compile.

2. In addition to aps.net, what are the features in. NET Framework 4.6? Does WF include? Does WCF include? Should Windows Form and WPF not include it?

--Now the. NET Core can be understood as in GitHub: Corefx and Coreclr,web Forms are not included, WCF contains only clients, Windows Form is not seen, WPF does not support.

3. Why does the. NET core go directly to 5 without the same version number as the. NET Framework?

The--.net Core and the. NET Framework are subset relationships, so the version number is independent.

Reference: Relationship between. NET core and. NET Framework, mono

Relationships between versions of. Net