How to handle huge efcore migrations designer files that is slowing down build and IDE

Question

I currently have an efcore 2.1 project with about 230 entities and about 350 migrations. Every time i add an efcore migration, a designer file is created. This file is approxima

Answer 1

I think your question is a duplicate of Recommended way to clean old Entity Framework Core migrations and Entity Framework Core: Is it safe to delete Migration.Designer.cs if we will never Revert a migration?. The whole topic is discussed in various answers on these threads.

I suggest to consider my answer in order to get your IDE snappy again and to reduce compilation time. And in the long run, it seems good practice to roll-up all migrations into one from time to time. If this is not urgent in your case, you might want to wait for this feature (planned for .NET 6) that allows you to do so in a simpler way.

Answer 2

You can try to purge your migration files. I sometimes use it to keep the data module small and compilable. You can find this link useful.

Answer 3

Now, in the future, it's possible to add an .editorconfig file to the Migrations folder, with the following contents:

# All files
# Sets generated code for all migrations
[*]
generated_code = true

It will disable all analyzers, which makes my IDE much happier with all the migrations.

Note: requires Visual Studio 16.5

Answer 4

You can use another assemblies to manage migrations.