EF5 Migrations - Duplicate/Re-defined variable bug when dropping constraints | Issue with usage of SQL GO command

Question

Background:

We have a project that uses ef-migrations containing multiple (read ~60) migrations created over a long period of development. Naturally, some of these

Answer 1

I put a Sql("--"); at the end of each migration. This runs OK as an applied migration and when I script the SQL I just do a find and replace on "--" to "GO". A bit manual but works for me. You could put Sql("--"); around your create trigger statements.