1

Closed

Remove Refactor-Rename from EF Designer

description

EF Team Triage: We will disable this feature again in EF6

Using the previous ("default") code generation strategy, refactor-rename on an entity or property traverses all the way through to application code and allows for easy renaming of classes in an existing codebase.

With the DbContext templates, refactor-rename from the diagram surface does not show any changes to application code. Applying the change regenerates the classes and breaks any code that uses the old class names. Refactor-rename from application code will also refactor the generated code, but these changes get wiped as soon as the code is regenerated.

This seems like a regression, but it might be easier to treat it as a proposed feature, since the code generation strategy has changed and refactor-rename would have to be re-implemented on top of it.

If the feature is removed - remove tests that are currently disabled (http://entityframework.codeplex.com/workitem/992) due to flakiness
Closed Dec 12, 2016 at 10:40 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

RoMiller wrote Aug 21, 2012 at 6:25 PM

Consider removing refactoring.

RoMiller wrote Apr 4, 2013 at 5:47 PM

If we do disable the feature then be sure to close this bug also - http://entityframework.codeplex.com/workitem/992 .

RoMiller wrote Dec 12, 2013 at 10:18 PM

EF Team Triage: Moving issues with Impact set to Low out of the 6.1.0 release as we only have time to address High and Medium issues in this release. We will re-triage these issues for future releases.

This does not exclude someone outside of the Microsoft EF team from contributing the change/fix in 6.1.0.