0
We use the same MS SQL database for several applications. I am aware that such action is not recommended but unfortunately it is the method that will have to be applied.
Work with code first and each time I create an application and try to run a migration in my bank, a code is generated that applies drop in the tables of other applications.
Currently in my Package Manager Console execution Update-Database -script and I manually adjust or even apply the same command in a local database and execute the code in my MS SQL database.
Is there any way to work simultaneously with several migrations without interference in another application if the tables have different names?
The scheme of Migrations supposes that all tables in a given schema are from one system only. The correct one would be a separation of schemas, and the tables of other systems appear as views of the schema in which there is the system with the EF.
– Leonel Sanches da Silva
I believe that Codefirst is not being used properly in your view... Databasefirst might be the best option... You can also disable Migrations... and even tell us which Clases you want to do Migrations, or whether it will be automatic when you start the system....
– Danilo Breda