There seem to be an incompatibility between ASP.NET WSAT/Membership and the EF Migrations. If I force the db context to create the database I can enable migrations and do database updates, but I can't use WSAT, it complains about not finding a stored procedure.
If on the other hand I let either WSAT (or Membership) create the database I cannot use the EF Migrations. (I can enable allright, but it does not create the initial migration and of course can't do any database update).
Has anyone experienced that issue and, more importantly, found a workaround?
Thanks,
Patrice
...
Go to the complete details ...