If you've been reading the EF Design Blog you will have seen
that we recently announced something called "FK Associations"
for the EF in .NET 4.0.  However in .NET 3.5 SP1, we only
support Independent Associations. What that means is that the FK
Columns aren't available as Properties in the entity. Which in
turn means you are forced to build relationships via References
to other Entities.  For example, unlike LINQ to SQL, this is not
possible in the EF:  product.CategoryID = 2;  Because there is
no "CategoryID" property in product entity.  You have to do
something like this instead:  product.Category =
ctx.Categories.First(c => c.ID == 2);  I.e. you need to use the
Category reference. Which means you have to have a Category in
memory, or do a query to get one like the example above.  The
problem is that not having a property for the CategoryID that
you can set directly can be a big pain, and that is why we've
added "FK Associations" and "FK Properties" in .NET 4.0.  All
well and good, but as Julie Lerman has