first code approach

You have to implement database initialization strategies inorder to update the database model. Below are the few ways how you can follow

CreateDatabaseIfNotExists: This is the default initializer. As the name suggests, it will create the database if none exists as per the configuration. However, if you change the model class and then run the application with this initializer, then it will throw an exception.
DropCreateDatabaseIfModelChanges: This initializer drops an existing database and creates a new database, if your model classes (entity classes) have been changed. So, you don't have to worry about maintaining your database schema, when your model classes change.
DropCreateDatabaseAlways: As the name suggests, this initializer drops an existing database every time you run the application, irrespective of whether your model classes have changed or not. This will be useful when you want a fresh database every time you run the application, for example when you are developing the application.
Custom DB Initializer: You can also create your own custom initializer, if the above do not satisfy your requirements or you want to do some other process that initializes the database using the above initializer.

Refer URL Simple Code-First Example (entityframeworktutorial.net)

3 Replies

Know the answer? Post it — somebody with the same question will find it here.

mani kandan5y ago
add-migration MyMigration -Context DataContext

update-database -Context YourContext
Sachin Singh5y ago
just create the class with desired properties then do
pm> add-migration createdNewtable

pm> update-database
follow https://www.sharpencode.com/article/EntityFramework/code-first-approach/start-from-scratch
Srinivasan Ramamoorthi5y ago
You have to implement database initialization strategies inorder to update the database model. Below are the few ways how you can follow
1. CreateDatabaseIfNotExists: This is the default initializer. As the name suggests, it will create the database if none exists as per the configuration. However, if you change the model class and then run the application with this initializer, then it will throw an exception.
2. DropCreateDatabaseIfModelChanges: This initializer drops an existing database and creates a new database, if your model classes (entity classes) have been changed. So, you don't have to worry about maintaining your database schema, when your model classes change.
3. DropCreateDatabaseAlways: As the name suggests, this initializer drops an existing database every time you run the application, irrespective of whether your model classes have changed or not. This will be useful when you want a fresh database every time you run the application, for example when you are developing the application.
4. Custom DB Initializer: You can also create your own custom initializer, if the above do not satisfy your requirements or you want to do some other process that initializes the database using the above initializer.
Refer URL Simple Code-First Example (entityframeworktutorial.net)