title: Foreign key navigation property naming convention alternatives
body: <p>When using Entity Framework 4.1, are there alternatives to the naming conventions for Navigation Properties?</p>
  
  <p>For example instead of doing this:</p>
  
  <pre><code>public virtual MyObject MyObject { get; set; }
  </code></pre>
  
  <p>To be</p>
  
  <pre><code>public virtual MyObject SomeOtherName { get; set; }
  </code></pre>
  
  <p><strong>UPDATE:</strong></p>
  
  <p>When the <code>[ForeignKey("OldStepId")]</code> and <code>[ForeignKey("NewStepId")]</code> attribute is added, the generated SQL then becomes:</p>
  
  <pre><code>{SELECT 
  `Extent1`.`CompletedId`, 
  `Extent1`.`OldStepId`, 
  `Extent1`.`NewStepId`, 
  `Extent1`.`Name`, 
  `Extent1`.`Step_StepId`, 
  `Extent1`.`Step_StepId1` 
  FROM `Completed` AS `Extent1`}
  </code></pre>
  
  <p>which, the last two columns do not exist. </p>