Controller necessary for creating database / Entity Framework

Dean Everhart 1,496

if I create a property set under models and list it in the context class and run a migration and database update the database is not created (as observed through MSSMS).

If I create a controller using entity framework in between creating a property set and the migration and database update, the database is created (as observed through MSSMS).

Am I correct in observing that a controller using entity framework has to be created in order for a database to be created through the migration and database update process?

(I thought perhaps a property set with the property set listed in the context would trigger the database being created).

AgaveJoe 26,141 Reputation points

2023-03-20T15:02:06.0066667+00:00
if I create a property set under models and list it in the context class and run a migration and database update the database is not created (as observed through MSSMS).

I cannot reproduce this behavior with Entity Framework Core and code first migrations.

If I create a controller using entity framework in between creating a property set and the migration and database update, the database is created (as observed through MSSMS).

Scaffolding????

Am I correct in observing that a controller using entity framework has to be created in order for a database to be created through the migration and database update process?

No. In my experience, migrations work exactly as illustrated in the official documentation.

Migrations Overview

(I thought perhaps a property set with the property set listed in the context would trigger the database being created).

In code first, you must execute two commands.

add-migration NameOfTheMigration update-database

The actual command lines could be a little different depending on how your project is setup if you are using the Package Manager Console or power shell.
Zhi Lv - MSFT 32,021 Reputation points Microsoft Vendor

2023-03-21T02:06:50.55+00:00

Hi @Dean Everhart

if I create a property set under models and list it in the context class and run a migration and database update the database is not created (as observed through MSSMS). If I create a controller using entity framework in between creating a property set and the migration and database update, the database is created (as observed through MSSMS).

Do you mean if use the "MVC Controller with Views, using Entity Framework" operation, you could create the database?

In the above scenario, whether you are using the same Data Context class? Whether they are using the same connection string? After migration, try to refresh the database in the SSMS, then check the tables.

I also check it on my side, both methods work well on my side (Using VS 2022, EF core 6).