Error when removing-migration

Describe the bug An error occurs when removing a previous created migration. Error: A relational store has been configured without specifying either the DbConnection or connection string to use.

To Reproduce Steps to reproduce the behavior:

1. Open Package Manger Console in Visual Studio
2. Create a new migration using the following command:
   add-migration AddSortOrder -context ApplicationDbContext -project Migrators.MSSQL -outputdir Migrations\Application -args “–provider SqlServer”
3. Remove migration using the following command: remove-migration -context ApplicationDbContext -project Migrators.MSSQL -args “–provider SqlServer”
4. Following error occurs:

System.InvalidOperationException: A relational store has been configured without specifying either the DbConnection or connection string to use. at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.get_DbConnection() at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.Open(Boolean errorsExpected) at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerDatabaseCreator.<>c__DisplayClass18_0.<Exists>b__0(DateTime giveUp) at Microsoft.EntityFrameworkCore.ExecutionStrategyExtensions.<>c__DisplayClass12_02.<Execute>b__0(DbContext c, TState s) at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerExecutionStrategy.Execute[TState,TResult](TState state, Func3 operation, Func3 verifySucceeded) at Microsoft.EntityFrameworkCore.ExecutionStrategyExtensions.Execute[TState,TResult](IExecutionStrategy strategy, TState state, Func2 operation, Func2 verifySucceeded) at Microsoft.EntityFrameworkCore.ExecutionStrategyExtensions.Execute[TState,TResult](IExecutionStrategy strategy, TState state, Func2 operation) at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerDatabaseCreator.Exists(Boolean retryOnNotExists) at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerDatabaseCreator.Exists() at Microsoft.EntityFrameworkCore.Migrations.HistoryRepository.Exists() at Microsoft.EntityFrameworkCore.Migrations.HistoryRepository.GetAppliedMigrations() at Microsoft.EntityFrameworkCore.Migrations.Design.MigrationsScaffolder.RemoveMigration(String projectDir, String rootNamespace, Boolean force, String language) at Microsoft.EntityFrameworkCore.Design.Internal.MigrationsOperations.RemoveMigration(String contextType, Boolean force) at Microsoft.EntityFrameworkCore.Design.OperationExecutor.RemoveMigrationImpl(String contextType, Boolean force) at Microsoft.EntityFrameworkCore.Design.OperationExecutor.RemoveMigration.<>c__DisplayClass0_0.<.ctor>b__0() at Microsoft.EntityFrameworkCore.Design.OperationExecutor.OperationBase.<>c__DisplayClass3_0`1.<Execute>b__0() at Microsoft.EntityFrameworkCore.Design.OperationExecutor.OperationBase.Execute(Action action) A relational store has been configured without specifying either the DbConnection or connection string to use.

Expected behavior Migration is removed.

Screenshots

Desktop (please complete the following information):

• Windows 10

[m-claes]

Hi, first let me thank you for your quick response and work on this project. Your proposed solution seems like a viable workaround. If the migration is not yet applied to the database a simple ‘Undo changes’ on Git could also undo the migration.

I haven’t been able to test the other featurese like token generation/endpoints as I was only working on the migrations part for a multi-tenant project (based on you article).

[1dveeran]

Sure I will try this. Thank you.