Unwanted migration for object mapped to view

Problem

We have an object

public class Foo
{
    [Key, Column(Order = 0)]public virtual int A { get; set; }
    [Key, Column(Order = 1)]public virtual int B { get; set; }
}

      

        
        
        
      

    

which needs to be mapped to an indexed view in SQL Server. Based on approaches

EF Code First: Displaying Non-Bit Objects with Fluent API and StackOverflow question

we first created an initial migration

public override void Up()
{
    CreateTable("dbo.Foos",
        c => new { A = c.Int(nullable:false), B = c.Int(nullable:false) })
        .PrimaryKey(t => new { t.A, t.B });
}

      

        
        
        
      

    

Then an empty migration where we added SQL to drop the auto-generated table and then add the index

public override void Up()
{
    Sql(@"DROP TABLE Foos");
    Sql(@"CREATE VIEW dbo.Foos As....");
}

      

        
        
        
      

    

finally, in our DbContext, Foo is mapped to the view:

modelBuilder.Entity<Foo>().ToTable("Foos");

      

        
        
        
      

    

This worked great until we added another property to Foo:

[Key, Column(Order = 2)]public int C { get; set; }

      

        
        
        
      

    

We have added a new migration to override the view

public override void Up()
{
    Sql(@"ALTER VIEW Foos ....");
}

      

        
        
        
      

    

The Alter View migration is being applied correctly, but EF thinks it should create a migration to account for the new property.

The database cannot be updated to match the current model because there are pending changes and automatic migration is disabled. Either write the pending model changes to a code-based migration, or enable automatic migrations.

When I ran

Add-Migration WhatIsPending

      

        
        
        
      

    

EF generates

public override void Up()
{
    DropPrimaryKey("dbo.Foos");
    AddColumn("dbo.Foos", "C", c => c.Int(nullable: false));
    AddPrimaryKey("dbo.Foos", new[] {"A", "B", "C" });
}

      

        
        
        
      

    

Question

Is there a better approach for mapping an object to a view so that changes to the object are painless?

If this is the best approach, how can I tell EF Migrations that it doesn't need to generate a migration?