title: Entity Framework "Invalid Column Name"
body: <p>We have converted an existing DB to use EF, so we write classes to map to our tables.  I've added a new column, a nullable int called 'iframeVideoId'.  I mapped it with</p>
  
  <pre><code>public int? iframeVideoId { get; set; }
  </code></pre>
  
  <p>and when I do a search of that table, it blows up with an '</p>
  
  <blockquote>
    <p>invalid column name' error</p>
  </blockquote>
  
  <p>.  This is a simple property it's not an index or related to any other table.  I tried renaming it in the DB to '<code>DisplayVideo</code>', and also making it not nullable.  Then I had</p>
  
  <pre><code>[Column("DisplayVideo")]
  public int iframeVideoId { get; set; }
  </code></pre>
  
  <p>Now I get an error that DisplayVideo is not a valid column.  Of course I have double checked that I am pointing to the right DB, and confirmed that every DB that my code COULD point to, has this column.  I've also done a clean and rebuild all, and rebooted my machine.  What could be wrong ? This is a basic column, and it's there.  I know from past experience that if the types did not match ( they are both int ), I'd get an error related to failed conversion between types.  This makes no sense to me at all.  I do not have an edmx file to refresh, because we're writing classes to map to the DB directly</p>
  
  <p>Just to add, I changed the column to a string and it makes no difference.  This is a new column, with a simple value, and EF claims it's not there.  </p>
  
  <p>And, I added the column to another table ( suboptimal, obviously ) and it just plain worked, immediately.  I'd still like to know why I have a table I can't add columns to in EF, though</p>