Using migrations with separate contexts for regular model and Identity

Question

I want my Identity data context (IdentityDbContext<IdentityUser>) and my regular EF model's data context (DbContext), to be separate.

Many say to merge them, but I don't see the point. They are very different, at least in my scenario, and I want to decouple them.

When I use initializers for each (CreateAlways, DropCreate, etc.), all works well. But I would like to use migrations for both data contexts - and I can only make it work for one, not both.

What is the secret to this?

score 0 · Answer 1 · edited May 23 '17 at 11:49

0

Does your to contexts reside in the same namespace? If so try to separate them into individual namespaces as suggested in this thread

edited May 23 '17 at 11:49

Community

1
1

answered Nov 12 '14 at 06:08

Indregaard

1,195
1
18
26

score 0 · Accepted Answer · answered Nov 14 '14 at 13:50

0

This is possible. It is necessary to set the parameters to the enable-migrations command, which allows more than one context per assembly, and to control each one separately.

answered Nov 14 '14 at 13:50

h bob

3,610
3
35
51

Using migrations with separate contexts for regular model and Identity

2 Answers2