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

Today, I would like to talk to you about the content of the .NET Framework version, which may not be well understood by many people. in order to make you understand better, the editor has summarized the following for you. I hope you can get something from this article.

The speed of technological innovation has reached a very fast era. This is undoubtedly a good time for a developer. These new technologies can help them improve the efficiency of program development. The .net new technology is constantly being renovated, and the .net version has been updated since 1.0. after 1.1,2.0,3.0, it has now reached 3.5. Many people exclaimed: the change is too fast, we have just learned one, the next comes again, it seems that there is always something to learn! In fact, when you fall in love with the IT industry, you should have the mental preparation of "never too old to learn". In the IT industry, it has also confirmed the fashionable buzzword "it is not easy to say love you".

The .NET Framework version is constantly updated, is it new wine in old bottles or old wine in new bottles? The answer seems to be the latter. Let's look at the following formula:

.net Framework 3.5 = .NET Framework 3.0 + .NET Framework 3.0 SP1

.net Framework 3.0 = .NET Framework 2.0 + .NET Framework 2.0 SP1 + WPF + WCF + WF + WCS

The .NET Framework version 3.5 is based on .NET Framework version 2.0 and .NET Framework version 3.0, including the .NET Framework version 2.0 and 3.0 Service Pack.

.net Framework 2.0 SP1: it updates assemblies contained in .NET Framework 2.0.

The .NET Framework 3.0 also contains the assemblies necessary for the technologies introduced in the .NET Framework 3.0. For example, WPF, etc.

.net Framework 3.0 Service Pack 1, which updates assemblies introduced in .NET Framework 3.0 (PresentationFramework.dll,PresentationCore.dll, etc.).

Applications use the same assembly regardless of whether they are targeting .NET Framework versions 2.0,3.0, or 3.5.

For example, an application that uses WPF for .NET Framework 3.0 uses the same mscorlib assembly instance as an application that uses Windows forms and targets .NET Framework 2.0. If the .NET Framework 2.0 SP1 is installed on your computer, mscorlib.dll has been updated and both applications will use the newer .NET Framework version of mscorlib.dll.

So, some people conclude like this:

.net 3.0 = .NET 2.0 SP 1 with WCF, WPF, WF and WCS

.net 3.5 = .NET 2.0 SP 2 with LINQ, C # 3.0, WCF 2.0, WPF 2.0, WF 2.0 and ASP.NET Ajax

It is worth mentioning that the relationship between versions 2.0,3.0 and 3.5 of .NET Framework is different from that between versions 1.0,1.1 and 2.0. The .NET Framework versions 1.0,1.1, and 2.0 are completely independent of each other, and for either version, you can exist on that computer, regardless of whether or not other versions exist on that computer. When versions 1.0, 1.1, and 2.0 are on the same computer, each version has its own common language runtime, class library, compiler, and so on. That is, the application can choose whether it is for version 1.0, 1.1, or 2.0.

.net Framework version comparison Table

.net packaged version 1.0 1.1 2.0 3.0 3.5

CLR version 1.0 1.1 2.0 2.0 2.0

C # Compiler version 1.0 1.1 2.0 2.0 3.0

VB Compiler version 7.0 7.1 8.0 8.0 9.0

.net Framework version compatibility

With regard to the compatibility of the version, here is the explanation of MSDN:

The .NET Framework's support for backward and forward compatibility is version-dependent. The .NET Framework supports backward and forward compatibility only for applications created with version 1.1. In applications created with version 2.0,. NET Framework does not support forward compatibility. In the context of the .NET Framework, backward compatibility means that applications created with earlier versions of the .NET Framework can run on a later version. Instead, forward compatibility means that applications created with a later version of the .NET Framework can run on earlier versions.

The .NET Framework provides a high degree of backward compatibility support. For example, most applications created with version 1.0 will run on version 1.1, and applications created with version 1.1 will run on version 2.0. Only for version 1.1,. NET Framework also supports forward compatibility. However, for forward compatibility, you may need to modify the application to make it work as expected. Applications created with version 2.0 will not run on earlier versions of the .NET Framework. For backward and forward compatibility, changes to the .NET Framework that improve security, correctness, and functionality may also cause compatibility issues.

After reading the above, do you have any further understanding of the .NET Framework version? If you want to know more knowledge or related content, please follow the industry information channel, thank you for your support.

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.