Applying migrations to upgrade from EF5 to 6.1.2 fails for SqlCE (CodePlex work items 2807, 2659) about ef6 HOT 7 CLOSED

Triage: we agree it may not always be reasonable to upgrade the EF version in stages, so we will try to fix this.

from ef6.

That sounds great, thank you!

from ef6.

we agree it may not always be reasonable to upgrade the EF version in stages

I seem to remember seeing this issue reported in the past between different, non-sequential versions. I thought we decided it was by-design.

Should I check every version back to 4.3 (where Migrations was introduced)?

from ef6.

The close reason for the original work item sounds close enough to "not worth moving the design if everyone can trivially work around it", but I don't know if that's "by design" as such. Maybe there was another work item and another resolution, though - it seems unlikely that only me and the reporter of the original work item ever ran into this.

from ef6.

@bricelam I think the idea was that we would make sure you could go from 5.0 to latest.

from ef6.

I think @bricelam and myself are in agreement that this can be closed as "Won't Fix" at this stage. From my perspective this is largely a point in time thing. I think we should have fixed this earlier, but we didn't, and at this stage adoption of EF6 is high enough that I think a workaround for folks moving from 5 is acceptable. "Acceptable" being different from "ideal" - I think we should focus engineering effort on other items.

Clearing up for triage so that this can be discussed. If others feel strongly that this should be fixed, then I'm fine with us doing that.

from ef6.

Only ever seen one customer raise this, so propose closing

from ef6.