JeePakaJP
JeePakaJP

Reputation: 840

After Core 3.0 upgrade, impossible to add-migration with EF Core 3.0

After upgrade core 3.0, it's impossible to add-migration in package manager. It's my error

PM> Add-Migration UpdateAlertTable -Context OozymContext
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation.
 ---> System.TypeLoadException: Could not load type 'Microsoft.EntityFrameworkCore.Internal.ProductInfo' from assembly 'Microsoft.EntityFrameworkCore, Version=3.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'.
   at Microsoft.EntityFrameworkCore.Design.OperationExecutor..ctor(Object reportHandler, IDictionary args)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor, Boolean wrapExceptions)
   at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture)
   at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
   at System.Activator.CreateInstance(Type type, Object[] args)
   at Microsoft.EntityFrameworkCore.Tools.ReflectionOperationExecutor..ctor(String assembly, String startupAssembly, String projectDir, String dataDirectory, String rootNamespace, String language)
   at Microsoft.EntityFrameworkCore.Tools.Commands.ProjectCommandBase.CreateExecutor()
   at Microsoft.EntityFrameworkCore.Tools.Commands.MigrationsAddCommand.Execute()
   at Microsoft.EntityFrameworkCore.Tools.Commands.CommandBase.<>c__DisplayClass0_0.<Configure>b__0()
   at Microsoft.DotNet.Cli.CommandLine.CommandLineApplication.Execute(String[] args)
   at Microsoft.EntityFrameworkCore.Tools.Program.Main(String[] args)
Exception has been thrown by the target of an invocation.

Upvotes: 9

Views: 5943

Answers (4)

Endi
Endi

Reputation: 17

In my case, the rootcause was a linked project with a different EF version in NuGet.

Upvotes: 0

Jucileudo Lima
Jucileudo Lima

Reputation: 11

The commands in the Package Manager console have changed. According to Nuget Gallery reference. follow below.

Add-Migration
Drop-Database
Get-DbContext
Scaffold-DbContext
Script-Migrations
Update-Database

Upvotes: 0

JeePakaJP
JeePakaJP

Reputation: 840

I had a reference of Microsoft.EntityFrameworkCore version 2.2.6 in a linked project which had the database connection string. I upgraded and it's works

Upvotes: 2

ury
ury

Reputation: 1160

I had the same issue after upgrading to version 3.0. After reading this, I installed the Microsoft.EntityFrameworkCore.Design nuget package and the problem was resolved.

Upvotes: 15

Related Questions