0

I'm starting to build a new web application from scratch where I want to use Microsoft's latest AspNetIdentity to manage logins and identities in my system. I have previously used asp.net Membership provider. There, at the beginning of application creation it was simply possible to create all the related tables and views of Asp.Net membership provider through a wizard or by running a simple command aspnet_regsql.exe on Visual Studio command prompt as described in this blog post.

I'm looking for something very similar wizard to get started with AspNetIdentity as well? I was reading lot of blog posts e.g. this which suggests that all the tables of AspNetIdentity will get automatically created through code first migration once you provide connection string to the DbContext.

But, I want to start from scratch or you can say DB first approach where I would like to see what all tables it creates then, add all my own required tables into the same database, build its relationships with aspNetIdentity tables to get started. Any help would be appreciated.

Community
  • 1
  • 1
RBT
  • 24,161
  • 21
  • 159
  • 240
  • it's just not like the membership provider was. Go to nuget and add it to your project then enable-migrations and add your first migration. Look in your migrations file and you'll see what it will create. – prospector Jun 20 '16 at 01:29
  • So the database first approach doesn't exist explicitly at all for using AspNetIdentity? – RBT Jun 20 '16 at 02:12
  • I've always used database first, generated the database, then populated my identity tables with identity. I don't know if there is a better way. – prospector Jun 20 '16 at 04:32

0 Answers0