Possible problems adding ASP.NET Identity on an existing database

Question

I want to use asp.net identity on a database that already exists.

I read this to do: How to add ASP.NET MVC5 Identity Authentication to existing database

but I am worried because I know asp.net identity uses code first, so can I lose my data? or it simply adds its tables to my db ? and in the future if I will update the asp.net identity package, can it drop the database?

** Now the database has only tables and some data (without others user/password tables)

As mentioned in the post you provided, you can easily add it to your existing database. So, there's no data lost. It just adds the tables to your database. You will only lose data if you specify your own database initializer (such as drop-create). Why do you want to drop the database when you update your Identity package? — Horizon_Net
– Horizon_Net, Commented Jan 21, 2015 at 16:15

prospector · Accepted Answer · 2015-01-21 16:30:41Z

1

You shouldn't have any problems since you don't have existing users. The only time you'd have problems with migrating existing users to identity 2.0, because the password hashing, but you'll be good to go.

Always back up your database before you make any changes to the database though.

answered Jan 21, 2015 at 16:30

prospector

3,4791 gold badge25 silver badges42 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Possible problems adding ASP.NET Identity on an existing database

1 Answer 1

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related