I don't like the Code-First-approach and want to make use of the new Identity-Features with my EF-mapped classes. I've got a table User with the columns
- Id (bigint, ai, pk)
- Login (nvarchar)
- Password (nvarchar)
The Interface Microsoft.AspNet.Identity.IUser enforces 2 properties:
- Id (string)
- UserName (string)
What, if I don't want to use this structure but I also want to do identity the right way?