Support DB-agnostic Models
Model should be DB-agnostic. One or more DB connections to a specific DB can be defined. These could be used for synchronization, XML mapping file generation etc. when requested by user. This way, a single model is maintained for more than one DB types. Now, there is not a simple way to accomplish this.
22
votes
pparth
shared this idea
-
Anonymous
commented
I have had to alter the template to duplicate GenerateFileHeader() so as to remove the .Entity.* and *.DataAnnotations references to achieve this.
Would be good in additional to the already present ability to separate Context and Model classes into separate projects.