EF6 Core – reconfiguring navigation properties, the runtime was complaining about a column GolferId being missing (invalid database column).
Took me a minute to figure out and remember the default foreign key dependency naming convention in EF. Sometimes these frameworks are a bit too intelligent for my taste.
Turns out the EF was guessing that if I have a navigation property to a related entity called “User” – the framework will automatically use an object property field called “UserId” 
… easily solved with the ForeignKey tag 🙂
https://stackoverflow.com/questions/46091157/changing-default-column-name-for-navigation-property
Center.is - Upplýsingatækniráðgjöf og Hugbúnaðarþróun 