I\'ve narrowed this down to some issue between Code First and Database first EF, but I\'m not sure how to fix it. I\'ll try to be as clear as I can, but I honestly am missin
In my case my seed method data was still calling a table column which had been dropped in a previous migration. Double check your mappings if you are using Automapper.