Home/ Questions/Q 7999655
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-04T15:33:57+00:00

We’ve generated ~80 migrations since the release of the 4.3.x version of Entity Framework.

  • 0

We’ve generated ~80 migrations since the release of the 4.3.x version of Entity Framework. Each time we generate a new migration, EF gens a snapshot of the current model for the IMigrationMetadata.Target property.

Since each migration is adding ~135k characters to our assembly, we are starting to hit critical mass. We’re now receiving a “No logical space left to create more user strings.” compiler error. Combine that w/ the pre-compile views, and you’ve got a lot of strings.

What’s the best long term approach to using EF migrations with a complex model?

Maybe add-migration should be generating these w/ resource files.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Thanks for reporting this. I have added this issue to our backlog for EF6.

    For now, replacing the string with a resource lookup is the best workaround I can think of.

    • 0