Hi Stephen, I haven't had a chance to work with Migrations on a real project. If you're happy for the users and roles, etc. to live in a separate context then I'd just enable Migrations for your context. As you say the asp.net is not going to change. As long as you have no conflicts in tables names (and you shouldn't because of schemas) you can set both connection strings to the same database.
If you are using transactions you want to be careful as if you're make two database connections within the same transaction (even if they are to the same database) I believe your app will attempt to promote the transaction to a distributed one and you'll enter DTC-land. Regards, Mike Michael M. Minutillo Indiscriminate Information Sponge http://codermike.com On Fri, Nov 16, 2012 at 12:23 PM, Stephen Price <[email protected]>wrote: > Hey all, > > I tried to turn on Enable-Migrations and got this message > > Enable-Migrations –EnableAutomaticMigrations > More than one context type was found in the assembly > > So whats normally done here? Do I merge my context in with the Asp.net one > that comes with the MVC template or do I enable it just for mine? (Am > assuming the asp.net one isn't going to change?) > > cheers, > Stephen >
