Skip to main content

Package Manager Console–Error when calling Update-Database

When trying to execute an EF Core migration inside the Package Manager console, I got the following error message:

An error occurred while accessing the IWebHost on class 'Program'. Continuing without the application service provider. Error: Please contact the administrator. The following database migrations are pending:

                        20190506091835_InitialCreate

Unable to create an object of type 'SampleContext'. For the different patterns supported at design time, see https://go.microsoft.com/fwlink/?linkid=851728

When browsing through the code to investigate the problem I noticed the following code snippet:

if (!Environment.GetEnvironmentVariable("ASPNETCORE_ENVIRONMENT").Equals("local", StringComparison.OrdinalIgnoreCase))
{
var serviceProvider = services.BuildServiceProvider();
using (var ctx = serviceProvider.GetService<SampleContext>())
{
var pendingMigrations = ctx.Database.GetPendingMigrations().ToList();
if (pendingMigrations.Any())
{
throw new Exception(
$@"Please contact the administrator. The following database migrations are pending:
{string.Join(Environment.NewLine, pendingMigrations)}
");
}
}
}

This code snippet was introduced to prevent executing migrations outside the local development environment. So maybe my environment was not correct?

I double checked the ASPNETCORE_ENVIRONMENT setting but this was set to ‘local’.

Why did this still fail?

The problem was that I was not running the application normally but using the Package Manager console to execute a migration. The Package Manager will use the default enviroment, explaining why I hit this error message.

To fix it I had to explicitly set the environment variable inside the Package Manager console:

$env:aspnetcore_environment="local"

Popular posts from this blog

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

.NET 9 - Goodbye sln!

Although the csproj file evolved and simplified a lot over time, the Visual Studio solution file (.sln) remained an ugly file format full of magic GUIDs. With the latest .NET 9 SDK(9.0.200), we finally got an alternative; a new XML-based solution file(.slnx) got introduced in preview. So say goodbye to this ugly sln file: And meet his better looking slnx brother instead: To use this feature we first have to enable it: Go to Tools -> Options -> Environment -> Preview Features Check the checkbox next to Use Solution File Persistence Model Now we can migrate an existing sln file to slnx using the following command: dotnet sln migrate AICalculator.sln .slnx file D:\Projects\Test\AICalculator\AICalculator.slnx generated. Or create a new Visual Studio solution using the slnx format: dotnet new sln --format slnx The template "Solution File" was created successfully. The new format is not yet recognized by VSCode but it does work in Jetbr...