[Jason]: ... I found myself needing the foreign key field on all the associations. Can I make a suggestion that the designer set the Foreign Key Property to [TargetEntity]Id by default unless user overrides?
[Michael]: I'm not a big fan of foreign key generation for the entities. They're really not an organic part of the model, and are only there to support the persistence mechanism. It's entirely possible to have a storage mechanism where they're not only not needed, but not possible, so that kind of change goes against the spirit of the extension. That being said, I can see adding the ability to globally add them on command; say, with a context menu command on the designer surface.
From the marketplace:
[Jason]: ... I found myself needing the foreign key field on all the associations. Can I make a suggestion that the designer set the Foreign Key Property to [TargetEntity]Id by default unless user overrides?
[Michael]: I'm not a big fan of foreign key generation for the entities. They're really not an organic part of the model, and are only there to support the persistence mechanism. It's entirely possible to have a storage mechanism where they're not only not needed, but not possible, so that kind of change goes against the spirit of the extension. That being said, I can see adding the ability to globally add them on command; say, with a context menu command on the designer surface.