6

I am looking to see if Extended Properties can be made to be part of Entities in EF 4.0, when the .edmx is generated or updated from the database. I also would like to see an example of running a stored procedure (function) from the .edmx in a T4 template, since I do have a procedure that returns the Extended Prop values.

Thanks

skaffman
  • 398,947
  • 96
  • 818
  • 769
user643258
  • 61
  • 3
  • Related to using the DB meta data in the EDMX file: [How can I make the Entity data model designer use my database column descriptions?](http://stackoverflow.com/questions/2747788/how-can-i-make-the-entity-data-model-designer-use-my-database-column-descriptions) – Daniel Ballinger Jul 27 '11 at 22:20

1 Answers1

2

So, a few things to bear in mind here:

  • The designer is not really extensible, but the provider is. That doesn't really help much because writing an EF provider is not a walk in the park. It's really complex.
  • The designer-related code, including the bits that relate to metadata, is mostly sealed and internal and almost completely unusable by you.
  • However, the EDMX file (the XML file itself) is very well documented: http://msdn.microsoft.com/en-us/data/jj650889 ... You can freely modify the XML yourself (by hand or through some Add-in or external utility), as long as you stick to the specifications.

The general idea is that you can use your own tool to read the extended properties and change the EDMX XML.

You will be adding "Annotations" to the SSDL (store metadata in the EDMX) elements. These Annotation values will be based on your extended properties of the relative entities in the DB.

Later on, when T4 executes, T4 receives the metadata collections based on the EDMX elements. This metadata will contain the Annotations you previously wrote there. Just about any element can have one or more annotations. You can then add custom code to the T4 template to handle the annotations that are based on your extended properties. The designer will not show the annotations, and you can't manipulate them in the designer, but it should preserve them (won't overwrite them if they are present in the EDMX).

Of course, this would be a lot easier if the designer was extensible, or even if the designer-related code was usable by you. Right now, that's not the case. Most parts of EF are moving to open-source, but the designer is still not there (yet). If the designer ever gets into open source, then you can probably make changes to start using that - and given that the community keeps asking for this kind of feature, I imagine the community will change the source to make it happen anyway. Until then, you have to manually edit the EDMX or write some tool to do it for you.

DevPrime
  • 901
  • 8
  • 5