Currently, when a foreign key is mapped, the HasForeignKey method is used, creating a 'foreign key assocation'.
This requires that the model has a the foreign key as a property of the class. Some users (eg. me!) might think that's a bit redundant, so [apparently the other way of doing this](http://stackoverflow.com/questions/15595818/mapkey-vs-hasforeignkey-difference-fluent-api) is to use the MapKey method.
It would be good to offer this as either an option, or possible a fallback if it is detected that the property doesn't exist.
This requires that the model has a the foreign key as a property of the class. Some users (eg. me!) might think that's a bit redundant, so [apparently the other way of doing this](http://stackoverflow.com/questions/15595818/mapkey-vs-hasforeignkey-difference-fluent-api) is to use the MapKey method.
It would be good to offer this as either an option, or possible a fallback if it is detected that the property doesn't exist.