Rider throws NullReference (on migrations add) while VS doesn't.

I cannot understand where is the problem... It cannot be with DB connection as you can see from the screenshot, all configurations are manually adjusted and I checked them 500 times. There is no problem with adding migrations in Visual Studio(( I believe that is Rider trouble. Maybe someone has seen something like that?

1 comment
Comment actions Permalink

Hi Sonnov2451,


dotnet will throw this NRE whether you are adding the migrations using Rider's built-in terminal or a system terminal/console. You can run dotnet ef migrations directly from PowerShell/CMD to verify this.


Could you check if you are properly creating the design-time DbContext for the migration?


Please sign in to leave a comment.