I have simple table definition in EF 6 code-first with simple foreign key.
public class Address
{
///
/// Gets or sets the id
This is just a convention of Entity Framework. If you don't like it, then you can enable migrations on your project and change the migration to not include the foreign key. I disagree with your assertion that it is inefficient, though.
To enable database migrations do the following:
Enable-Migrations
Add-Migration InitialMigration
Up
method with a few statements. Find the line that adds the foreign key and remove it.Update-Database
to apply migrations.This is assuming you do not have a database yet and are starting from scratch.