What is the idea behind a DbContext class (EF)? Should I have one per model, one per application or maybe something else?
I guess I don't understand what they're used for. I get that I can put my data fetching logic in there, and that's great, but in that case, it seems to me that I should have one per model. Although if I have one per model, VS will create one connection string for each DbContext, ie. for each model. I'm surely missing something here.