You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
as from subject, when I use a db context with an existing db used by an existing application, happens that this application receive updates that update the db schema. I know I can update the POCO classes to reflect the new schema, but if I have updates to multiple tables a tool to do this automatically may be very useful
The text was updated successfully, but these errors were encountered:
Its really important to have it. Since we wont have EDMX support.
I think its ok to have a EDMX like file (designer only), to keep metadata about the mapping
Part of this is supported already in the reverse engineer process we have in EF6 (which will be the first level of functionality we provide in EF7). You can re-reverse engineer the model and it will update the existing code. Some level of customization can be done by using partial classes etc. for any customization you make to the code (or modifying the T4 templates used during the reverse engineer process). This is far from perfect though because there are some customizations that are hard to do in a separate class without modifying the scaffolded code.
as from subject, when I use a db context with an existing db used by an existing application, happens that this application receive updates that update the db schema. I know I can update the POCO classes to reflect the new schema, but if I have updates to multiple tables a tool to do this automatically may be very useful
The text was updated successfully, but these errors were encountered: