is. NET Core 2.0 The best choice for you?

This month, 14th, Microsoft released the official version of the. NET Core 2.0, and its release means that the. NET core platform is more mature and a better future. This article will analyze the features and future directions of. NET core and provide a reference for developers to choose which platform to develop programs for.. NET core 2.0 is your best choice. 1. NET core 2.0 features 1.1. NET core platform is open source 1.2 cross-platform 1.3 Flexible Deployment 1.4 Modular Architecture 1.5 command line tools 1.6 Cloud support 2,. Net Core follow up Roadmap 2.1 release schedule for known major releases 2.2. NET core history 3,. NET core or. NET Framework? 3.1 Overview 3.2 Select. NET core or. NET Framework summary 1,. NET Core 2.0 features 1.1. NET core platform is open source

The. NET core is part of the. NET Foundation, as shown in the following illustration:

The. NET Foundation is a community that surrounds the. NET development framework and is constantly innovating. Another big step for Microsoft is to make ASP.net core open source. Because it is an open source platform, you can better control the use and modification of it, and the transparency of its code can provide information and inspiration for your own. NET core projects. In addition, you and your partner can quickly correct errors and circumvent security risks to make. NET core more secure.. NET core is more stable because the code for the Platform tool remains open. The entire framework source and package can be found on the GitHub site. 1.2 Cross platform

In addition to making it open source, Microsoft has spared no effort to make it cross-platform. Developers will be able to develop applications on Mac,linux or Windows systems. In fact, it also introduces a new code editor, "Visual Studio code," that is specifically provided for Mac and Linux users. 1.3 Flexible Deployment

This feature of the. NET core helps developers flexibly deploy as part of an application (the fdd-framework relies on deployment) or as a new installation (scd-standalone deployment). FDD allows you to minimize the use of memory and disk space with a smaller deployment package, while SCD has full control over project deployment, including. NET core libraries and runtimes. 1.4 Modular Architecture

This feature helps developers to use only the necessary packages based on the requirements of the project. A modular architecture helps upgrade its cross-platform compatibility. As a result, developers can now design lightweight, efficient, and powerful applications. The new version is relatively lighter and smaller than previous versions, which helps speed up the development process. A significant change to the file system will help build a robust development environment. 1.5 command line tools

The new version is lighter and smaller than previous versions, which helps improve development efficiency. In order to build a robust development environment, the file system has made great changes. Each possible product scenario can be accessed at the command line named DNVM or dot net version manager. This command line can be easily updated and configured. NET Runtime. This is. NET execution environment. Another benefit of the command line is that it has nothing to do with the platform, and developers don't need to learn the tool chain again and again. Once you are familiar with its use, you can use the same approach on any other supported platform or interface. 1.6 Cloud Support

ASP.net Core is the first to develop a feature that keeps the flock in. Because it supports cloud-based configuration, cloud initialization settings allow developers to easily publish their applications to the cloud. 2. NET Core follow up development roadmap 2.1 Release schedules for known major releases

version	Publish Time
1.0 RC1	February 15, 2016
1.0 RC2	May 16, 2016
1.0	June 27, 2016
1.1	November 16, 2016
2.0	August 14, 2017
2.1	2017 Quarter Iv.

2.2. NET Core Development Process 1.0 RC1

January 2016 asp.net 5 renamed ASP.net Core 1.0, all name changes as shown below:

1.0 RC2

. NET core spans each platform: that is, all application models built on. NET core (e.g., asp.net Core, Console Apps, and class libraries) can be run not only on the Windows system, but also on the OS X and Linux systems. 1.0

The downloads (https://www.microsoft.com/net/download) provided by the Microsoft team include the. NET core Runtime, the. NET core SDK,. NET core VS tooling (including WEB development tools) ,. NET core Windows Server Hosting, and the updated NuGet asp.net core 1.0 and Entity Framework Core 1.0 packages. Microsoft has also released Visual Studio and Visual Studio Code extensions for creating. NET Core projects, as well as. NET documentation (https://docs.microsoft.com/zh-cn/). 1.1

. NET Core 1.1 release, this version supports the validity period of three months, followed by a change.
11/16. NET Core 1.1 RTM release. The corresponding release asp.net core 1.1, EF core 1.1. Visual Studio for Mac is also published together. You can create a. NET Core 1.1 application through Visual Studio 2015, Visual Studio 2017 RC, Visual Studio Code and Visual Studio for the Mac. 2.0

Supported by the visual Studio 2017 15.3 release and introduced a new Razor Pages user interface design paradigm. For ASP.net Core, this version simplifies deployment and improves preload page performance. People are more concerned about the changes brought about by the supporting. NET Core 2.0 platform: Reducing the barriers to getting started and learning,. NET Standard 2.0 makes it easy to cross through a standardized shared API. NET Framework,.net core and Xamarin shared code. The. NET Framework 4.6.1 supports. NET Standard 2.0,.net Standard 2.0 adds many. NET Framework 4.6.1 Branch API. NET Standard 2.0 has added 14,994. NET Framework 4.6.1 already supported APIs. NET Standard 2, and Standard 2.0 has its own API. The ET Framework 4.6.1 Unsupported API. NET Standard 2.0 will be a superset of. NET Standard 1.6. In other words,. NET Standard 2.0 and 1.x will not have a breakthrough.. NET Framework Compatibility Mode: allows. NET Standard projects to refer to. NET Framework libraries, leveraging. NET, which facilitates the development platform to migrate from the. NET Framework to. NET Core.

Ultimately, it can be understood that. NET Core 2.0 will be equivalent to the. NET Framework 4.6.1, while existing. NET Framework code can be easily ported to the. NET Core platform 3. NET Core or. NET Framework? 3.1 Overview

The. NET Framework supports Windows and Web applications. Today, you can use Windows FORMS,WPF and UWP to build Windows applications in the. NET framework. asp.net mvc is used to build Web applications in the. NET framework.

The. NET core is a new open source and cross-platform framework for building applications for all operating systems, including Windows,mac and Linux.. NET core supports UWP and asp.net core,uwp for building windows 10 target Windows and mobile applications, asp.net core is used to build browser-based Web applications. The following figure allows you to see the main functional differences between the. NET core and the previous. NET Framework:

The same asp.net Core differs greatly from the traditional asp.net, as shown in the following illustration:

3.2 Select the. NET Core or the. NET Framework

by application level.

Product requirements	.net core/framework
Windows Client applications using Windows Forms and WPF	. NET Framework
use Applications for libraries such as WCF,WF	. NET Framework
the third-party. NET libraries or NuGet packages that you need to use cannot be used with. NET Core	. N The ET Framework
needs to use. NET technology that is not available for. NET Core	. NET Framework
you need to use a platform that does not support. NET Core	. NET Framework
pre-configured environments and systems	. NET Framework Better
is supported for Dockers container support	, but. NET core is more appropriate for
Micro-service	can be, but. NET core is better for
Cross-platform requirements	. NET Core
requires a high-performance and extensible system	. NET Core
needs to select a parallel. NET version	. NET Core

Summary

It is not surprising that the. NET core platform has grown rapidly since 2016. Microsoft has accumulated many years. NET Framework experience before it was born. From the above we can see Microsoft's strategy: The first step is to achieve a cross-platform second step is to make it and beyond the current. Net The capabilities of the framework the third step is to achieve the unified platform development and operating environment, including the end (server, handheld devices, IoT, etc.)

now see the first step is very high, the second step is completed 70% (by the number of APIs). The third step has been done. We can see a bright future from Microsoft's development line. NET language to a variety of devices to write a program is enough to meet product demand, this is a win-win situation. We also sincerely hope that. NET Core has a better future.

Author: The origin of the Handsome worm: http://www.cnblogs.com/vipyoumay/p/7388371.html