This project is read-only.
23

Closed

Enable migrations for the EF Designer (EDMX models)

description

This item was migrated from the DevDiv work item tracking system [ID=6096].

This work item originated from connect.microsoft.com. A member of the EF team at Microsoft should close the related Connect issue when closing this work item.
Closed Dec 8, 2016 at 10:42 PM by RoMiller
EF Team Triage: We are transitioning this project to GitHub (https://github.com/aspnet/EntityFramework6). As part of this transition we are bulk closing a large number of issues in order that our new issue tracker will accurately reflect the work that our team is planning to complete on the EF6.x code base.

Moving forwards, our team will be fixing bugs, implementing small improvements, and accepting community contributions to the EF6.x code base. Larger feature work and innovation will happen in the EF Core code base (https://github.com/aspnet/EntityFramework). Closing a feature request in the EF6.x project does not exclude us implementing the feature in EF Core. In fact, a number of popular feature requests for EF have already been implemented in EF Core (alternate keys, batching in SaveChanges, etc.).

This is a bulk message to indicate that this issue was closed and not ported to the new issue tracker. The reasons for not porting this particular issue to GitHub may include:
  • It was a bug report that does not contain sufficient information for us to be able to reproduce it
  • It was a question, but sufficient time has passed that it's not clear that taking the time to answer it would provide value to the person who asked it
  • It is a feature request that we are realistically not going to implement on the EF6.x code base
    Although this issue was not ported, you may still re-open it in the new issue tracker for our team to reconsider (https://github.com/aspnet/EntityFramework6/issues). We will no longer be monitoring this issue tracker for comments, so please do not reply here.

comments

ESSB wrote Oct 5, 2012 at 11:08 PM

Hi,

I have raised this at: http://social.msdn.microsoft.com/Forums/en-US/adodotnetentityframework/thread/c63bf034-f205-4b4e-82e0-40b1c3fca71d where there is extra information. I believe this is important since this works fine in VS2010 SP1 via the Powerpack, and the absence of this in VS2012 prevents me from migrating to VS2012. I think this is a fabulous feature ie Migrating a Database from a Model without data loss.

Really hope it can be resolved quickly.

Many thanks,

Edward

jhurdlow wrote Mar 11, 2014 at 2:16 AM

Model-First in EF is effectively useless without this. I previously did this with the PowerPack in VS2010. I just spend a bunch of time doing a new model-first project in VS2013 only to find this is now not viable. Simply not acceptable. :(