(ii) the ASP. NET Identity Persistence separation

From the version of Visual Studio 2013 to Visual Studio 2015, the implementation of the ASP. NET identity is included in the project template in the new MVC project, but it is not known how many people will use the existing identity template directly, I had intended to use it directly in a recent project, but found that there were too many things I didn't need and looked bloated. This article mainly describes the process of splitting the entire MVC project.

The understanding of this article requires a basic understanding of the ASP. Read the relevant article: Https://www.asp.net/identity or

Directory:

• Problems with the default template

When you create a Web application that uses the MVC template, the new project you will find is single-layered and tightly coupled to the Entity Framework. Problem:

1. The single-layer architecture is mixed with repository mode, unit of work mode, and dependency injection, and convenient unit testing is actually a little more convenient.
2. The Iuser interface must be implemented in the user's entity, with the net identity in a tightly coupled state.
3. Entities, persistence, and business logic are all in one piece.

(ii) the ASP. NET Identity Persistence separation