Open source ASP. NET Core Small Community system

Objective

Hope the Stars hope the Moon, ASP.

I was still in junior high school when ASP was released and didn't catch up. But I've been focusing on the beta version of ASP. The original project was named ASP. VNext and then renamed ASP. NET 5. The most painful is the RC1 release, the official continued to release the name change and RC2 extension notice. I have done some demo projects during this period, but since beta to RC2 involves a lot of API changes, including the Dnx->dotnet CLI, including various namespaces and tool name changes, and so on, so this part of the demo has been deleted. In May, the Github ASP. NET core updated the roadmap to determine that RC2 was released in mid-May, and that RC2 will be the basis for the final release. During that time, I was crazy about GitHub, even in foreign honeymoon, will be at night to rub WiFi attention dynamic (here to mention, have time to look at the issue of each project, can accumulate a lot of knowledge. At the same time, a lot of gossip can be seen in the Members ' replies. Fortunately, the next no-jump, open source, cross-platform, high-performance ASP.

Small Community Systems

First look at the following items:

Project layout Reference Cnodejs front-end adoption of bootstrap, database access with EntityFramework Core, while using middleware to achieve a simple identity authentication function

Currently completed functions: registration, login, post, replies, collection, top, essence and other functions.

Project Address: GitHub

How to run:

1. Install the base environment first

2. Clone or download the project, first set the connection string, and then restore the database, and finally run

Detailed process please click on the above link to view the project homepage

Development feeling 1. For beginners, the entry threshold for ASP. NET core is still quite high.

Without WebForm, you can no longer drag and drop the control to complete a Hello World Page.

MVC and Webapi are merged, so at least there should be some basic understanding of these 2 technologies.

Processing HTTP requests from the traditional handler, page into the middleware, if not familiar with Nodejs (Express) is a new thing.

Build a Web project, the first is to use the dependency injection container, and how many beginners have been exposed to dependency injection?

2. For. NET developers, there's a lot to learn.

The new Taghelper and viewcomponent, it seems, is to cultivate the habit of building-oriented programming.

The front-end can be conveniently integrated bower, gulp and so on, then Nodejs, NPM, Bower, Gulp and so on are needed to learn.

Project.json inside the things involved in the compilation, release, Deployment and so a series of configuration, combined with dotnet command, can be very simple to automate, think it is not very excited?

New EntityFramework Core Migration, directly based on commands to generate and update databases, does it look cool?

The entire ASPNET Core framework is open source, the basic source does not want to see?

The most important is the cross-platform! Now we can no longer escape from Linux, everyone quickly installed virtual machine, from the most basic LS to start the Linux tour!

3. There's still a long way to go for ASP.

Performance: From the official performance test, the current ASP. NET core can be more than Nodejs, but it is still much worse than Java Netty (this test looks like a RC1 version). First of all, I think we should develop a good habit of asynchronous programming, this article describes how asynchronous programming improves concurrency efficiency, and second, we can only hope that Microsoft will continue to improve performance, or have a third-party high-performance web framework appears.

Framework: ASP. Net Core has declared only a subset of the. Net framework from birth, but the lack of some of the underlying frameworks has been a major inconvenience. The most inconvenient thing is system.drawing.

Third party libraries: As a baby, ASP. NET core is just born, and has experienced jumping tickets, so the resources are very poor. Some of the most popular items: Dapper,automapper,nlog and so on have been very early support.

Developer Churn: Who dares to say that there is no one around. NET to Java, go to Android, go to iOS??

Postscript

Yesterday overtime to 3 o ' clock, continue to work this morning, the head is dizzy. Personal technology is not good, the opinion is not enough, the above are their own ideas, I hope we have a lot of exchanges, together for. NET community to contribute!!

Open source ASP. NET Core Small Community system