Learn about the issues shared with ASP. NET Core 2

. NET Core was released from June 28, 2016, almost a year ago, but at work it was found that the acceptance of. NET core was not high, it was just a feeling that "there is no say without investigation", two days through the small program in the group to do a survey, The number of people involved is about 230, and as a result, everyone is waiting for. NET Core 2.0, expecting that. NET Core 2 will be available on time in 7 August. The problem with this survey is that there are 3 situations in which I voted directly on the use of. NET Core:

There are only 26% people using. NET core 1.0/1.1 and the plan is to use. NET Core 2 to reach 59%, with no plan to use. NET core at a scale of only 14.4%. From this result, we still look forward to. NET Core 2.

As the next-generation platform for the. NET Framework, the biggest change is ASP. The most hot topics of the current ASP. S is a cross-platform experience, which is a huge achievement, but if you're a regular ASP. Users, write a lot of basic. NET 4.x code, and intend to continue to use the familiar IIS and Windows environments, then this is not an add-on. This is also a good explanation of why the current percentage of users using. NET core 1/1.1 is not high.

Looking back 15 years ago, the ASP was used by most of the ASP's best practices when designing the ASP, and these practices were adopted in the new framework. In the process, they also introduced many new content, such as compiled code and managed code, automatic postback, and server controls. The same routines evolve with ASP. Asp. NET common best practices such as initial load configuration data, Dependency injection, NuGet packages, claims-based authentication, and Razor improvements are native features of ASP. ASP. NET core also has different boot processes, more modular request-response middleware, and a more flexible infrastructure for defining controllers and views. ASP. NET Core is also a cross-platform framework that allows you to develop and deploy applications on Windows, MacOS, and Linux. In this way, ASP. NET Core will force you to write better code, that is, the default force to achieve separation of concerns, of course, you can also achieve this goal through self-discipline in a very small number of ways.

For the development of any form of new project (product), the ASP. NET core is definitely the preferred, and it is well explained that most users plan to adopt. NET Core 2.0, which is aligned with the. NET Framework 4.6.2. However, as a new framework, some initial costs are unavoidable: All team members must be proficient in this framework. In addition, all members must also be proficient in the model-view-Controller (MVC) application model.