Auto Migration in .NET Core

Chisom Nwike — Thu, 20 May 2021 12:38:45 +0000

This is a really straightforward activity.
Using EF Core code-first approach in .NET Core applications we always tend add migrations as our application entities change.

Do we really need to always run the update-database command. I think not.

put this code snippet anywhere you find comfortable in ur project

private async Task RunMigration<T>(T db) where T : DbContext { List<string> pendingMigrations = db.Database.GetPendingMigrations().ToList(); if (pendingMigrations.Any()) { IMigrator migrator = db.Database.GetService<IMigrator>(); foreach (string targetMigration in pendingMigrations) { migrator.Migrate(targetMigration); } } await Task.CompletedTask; }

Also, say you have multiple contexts, notice how the snippet above uses generic type to handle any context that inherits DbContext.

The last step will be to add RunMigration(yourDbContext) to your Startup.Configure method.

Have fun!!

dotnet quit unexpectedly

Chisom Nwike — Thu, 09 Jan 2020 02:25:29 +0000

Hi guys,

It's the first work week for some of us in the year and you probably just decided to enjoy the comfort of the your updated Visual Studio for mac. You have written a long and pleasurable art and it's time to see it running so you can satisfy and reward your mind's effort at this new art but some how, this image above shows up and you want to go BONKERS!!!😭😩🤬

Just take a deep breath, calm down. You will be fine because I got your back. 😘💕

I believe, VS for Mac is still a work -in- progress but not so much of an excuse for the team that code / service related issues cannot be reported in the IDE's Application Output.

Here is what you might have to do to get your issue resolved.

In your IDE, right click on the project and select "Reveal in Finder".
Open your Terminal and cd to the Project's Location (the folder containing .csproj file).
Type in the command :- dotnet run

This will give you a detailed error message and stack trace to help you figure out what the issue might be with your app at startup-time. Fix this and you will be just fine again.

Some Frequent Reasons for this will be:

The Port for your app is already in use :- kindly check that port 5000, 5001 or any port configured for your app is not currently being used by another application.
Service Dependencies :- Also check that you have properly configured all your app's dependencies in your startup class or autofac container (whichever one you use).

There might be other issues with your code, please share your own experience and help the community.

Have a Lovely day at work!😍👌🏾

DEV Community: Chisom Nwike

Auto Migration in .NET Core

dotnet quit unexpectedly