Created Issue: Migrations - Moving Schema and Dropping Foreign Key Bug [759]

I changed the schema of one of my tables (the project is still in development so it isn't a big deal) and the migrations code that was generated was seemingly not aware of this change. Here is an example of the code that the migrations tool generated from the Add-Migration command:

MoveTable(name: "General.SomeTable", newSchema: "Debug");
DropForeignKey("General.SomeTable", "SomeForeignkeyId", "General.SomeOtherTable");

Notice how the new schema is Debug but the following line of code still thinks the schema of SomeTable is General. It is easily fixable by hand but I would prefer the migrations tool to be a bit smarter.