Are you still having issues with this? Seems to be the same problem in a similar thread. Can you turn on debug logging or entity framework, should be able to see some logging on while it is failing on Integration
Any update regarding this issue ?
I assume when you deploy from INT to Preproduction then database is not updating. While deploying from PaaS portal are you checking "Use maintenance page"? I notice database schema updated when you check this checkbox. Probably worth trying.
I am using foundation for a new project we have, I am facing an issue where the table is not getting created via EF Code first approach. It works when I do the update-database via the NuGet console on local. But after deploying to Integration on DXC it did not work. There was a similar issue earlier on this forum, I am doing all that was suggested on that topic, but the issue still persists. Below is all the code related to it:
I then ran the Enable-Migrations commad, and then Add-Migration TestTable. This then creates a Migration folder along with the 2 classes below:
I then added a new Initialization for this:
I also get an error that Entity Framework 6.4 does not have the migration files, upon looking into the package I did not find any migration files under the tools folder in the EntityFramework.6.4.0 nuget package and hence went down to 6.2.
Also, while I was debugging on Inte; I see that the seed method is not being triggered. On local the moment I we enter the update-database on the Nuget Console, it triggers the seed method.
The update schema app settings config is set to true, the connection string name is correct amd the custom initialization module has a dependency on EPiServer.Web.InitializationModule. Since I am using foundation and have not made any changes to the configurations, my expectation was this should be a smooth sail. But it doesnt seem to be the case, is there any configuration I need to turn on/off.