I have a database that is changing a lot and i am constantly having to go into the data context designer and manually set a number of associations child properties to false. Each time i delete the table from the designer i have to go back in and redo all the associations.
Is there a way to use a partial class to define what the association child property is on say an entity called Company which has a one to many relationship to an entity called Program?
My hope is that i can simply change the association child property in code so that each time the entity is removed from the data context and re-added, i dont have to go through the whole process again.
Thanks for any help!
I have been watching this question, hoping someone has better news for you than I do. You can in fact add a partial class in the same namespace as your context and within there define new name for the child property/collection (it is so annoying to have it re-generate as User1, User2, User3 when you have defined it as OpenedBy, ApprovedBy and ClosedBy or some similar such thing).
This does help with being able to access the properties by a more friendly name, as you have expressed above; however I have not found a way yet to, in that partial class, define the property such that it maintains all the properties (pun not intended) of Entity Framework navigation properties with full read/write functionality.
It doesn’t solve your problem, but as far as I know, it is an accurate answer; I have moved on and just accepted that I will have to rename navigation properties in the EDMX in the case that I have to drop/re-add an entity.