Entity Infrastructure Migration: .resx Snapshot vs. __MigrationHistory Table

Following my question on Entity Framework Migration: why does it ignore the snapshot and take __MigrationHistory into account? , I am confused, why do EF migrations store the previous model both in the database inside the __MigrationHistory table and in the resource files? And even more vaguely, why does he completely ignore the resources and consider the table data to calculate model changes?

+4

entity-framework code-first-migrations

Hans Jun 14 '15 at 5:53

No one has answered this question yet.

See similar questions:

1

Entity Framework Migration: why does it ignore the snapshot and consider __MigrationHistory?

or similar:

783

Entity Framework vs LINQ to SQL

630

The fastest way to embed Entity infrastructure

237

Reset Migrations Entity-Framework

183

Entity Framework 4 / POCO - Where to Start?

151

Rollback Entity Framework and remove bad migration

3

Entity Framework Migrations Under the Hood

2

Update snapshot of last migration model in Entity Framework and reuse it

1

Entity Framework Migration: why does it ignore the snapshot and consider __MigrationHistory?

1

Why does the Entity Framework Migrations store the entire model and not the hash in the __MigrationHistory table?

0

How to exclude an entity and its properties in Entity Framework migrations?

All Articles