**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
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