What is the point of creating foreign key properties when using Entity Framework Code First?
Yes, I think there is no need for foreign key properties and they are somehow a relational artifact in the object world. You can define relationships completely without FK properties. In Fluent API you can define if the relationship is optional or required and you can specify the database table's foreign key column name.
The relationship is then called Independent Association .
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.
Related Questions
Why am I getting an extra foreign key column with Entity Framework Code First Foreign Key Attributes?
Entity Framework 4.1: How can I access virtual entity properties after creating a new entity?
Asp.net MVC 2 relation without Foreign Key with Entity Framework 4 Or With Foreign Key?
Entity Framework Code First Mapping Foreign Key Using Fluent API?
Entity Framework Code First : Setting up One-To-One foreign key association using Annotations?
If a foreign entity authorized to transact business in Colorado merges with another foreign entity, how can the entity record the merger in the state of Colorado?