1
Vote

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

comments

RoMiller wrote Aug 21, 2012 at 5:25 PM

Consider removing refactoring.

RoMiller wrote Apr 4, 2013 at 4: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 9: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.