Of course, migration functionality is not dependent on where the Configuration.cs file is. You may freely move it. When you call migration scripts it will still search for Configuration class in whole project. Remember only about properly setting MigrationsDirectory property within Configuration class - it points to folder where you have your migration classes defined.
Change Migration Configuration Location
-
15-07-2023 - |
문제
Is there a way of changing the location of the Migrations/Configuration.cs file to another location without breaking EntityFramework migrations?
해결책
제휴하지 않습니다 StackOverflow