You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At this point (step 8), it would seem to me that since there were no changes to the model since the scaffold, there would be no updates. Dotnet-ef-database-update attempts to recreate the entire database schema. I think there used to be an -IgnoreChanges switch on add-migrations to help with this issue.
The goal
I want to start database first and have dotnet-ef-dbcontext-scaffold perform the heavy lifting of creating a ton of classes and setup the object relations based on the database schema. Then I want to switch to code-first; add Identity Framework to the project; and use dotnet-ef-migrations-add to add the identity tables using a migration then continue in a code-first fashion from then on. Perhaps my approach is wrong?
Proposal #1 from #2167 "...add a way to point our reverse engineering engine to the existing database to obtain a model snapshot (and possibly an accompanying initial migration)." would seem to address the issue.
Steps to reproduce
The issue
At this point (step 8), it would seem to me that since there were no changes to the model since the scaffold, there would be no updates. Dotnet-ef-database-update attempts to recreate the entire database schema. I think there used to be an -IgnoreChanges switch on add-migrations to help with this issue.
The goal
I want to start database first and have dotnet-ef-dbcontext-scaffold perform the heavy lifting of creating a ton of classes and setup the object relations based on the database schema. Then I want to switch to code-first; add Identity Framework to the project; and use dotnet-ef-migrations-add to add the identity tables using a migration then continue in a code-first fashion from then on. Perhaps my approach is wrong?
Further technical details
EF Core version:
Operating system: Windows 10 Enterprise
Visual Studio version: VS 2015 Enterprise
The text was updated successfully, but these errors were encountered: