New. NET Core road map and. netcore Road Map

New. NET Core road map and. netcore Road Map

. NET Core/ASP. two weeks after the release of NET Core 1 RTM, the Community was also very active and received a lot of feedback. Microsoft scott Hunter posted it on the dotnet team's official blog last Friday. NET Core, a new road map ,. @ Lex_Li has a brilliant Weibo comment:

Next we will talk about our. NET Core roadmap on the microblog of @ lex_li.

1. There are also a lot of people who are already using Version 1.0, but many people think it lacks many things .. NET Core 1.0 is only a pure subset of the. NET Framework and has no difference in features. There are still a lot of API missing, and the users who are already using it are working on their own to fill up the missing libraries. For example, Jexus 5.8.2 beta has fully supported ASP. for more information, see ASP. NET Core "complete release, built-in RunTime" to jexus, blog Park also launched a site. NET cross-platform: The first ASP running on Linux is launched in the production environment.. NET Core site. Those still waiting for a while are about to wait till Q2, and there is a patch 1.0.1 in March.

2. the next version is mainly to provide improved vs tools, mainly to replace. csproj/MSBuild. xproj/project. json, And. NET Core SDK will reach 1.0 RTM. At this time, the. NET Core Runtime and Tools have reached the 1.0 RTM level, maintaining stability and high performance. The latest time is Q1 in 2017, and Q4 in 2016 will be successful. At the same time, C #7 and VB 15 will be ready. In this case, Visual Studio (2016/2017) you can also use it.

3. Q1 2017/Q2 2017 will release a version that everyone is looking forward to. A large number of students will release this version after it is released.. NET Core is imported to your environment for development and deployment. This version adds a lot of APIS, including network, serialization, and data. At the same time, Microsoft will continue to update.. NET Framework ,.. NET Core will be transplanted.. NET Framework. Microsoft will minimize API and behavior differences to avoid damaging the existing.. NET Framework Application compatibility. Then there will be a. NET Standard 2.0. This version should be able to achieve the goal of the following figure: