Questo è quello che sto usando solo sulla modalità di rilascio per generare gli script:
public class MigrationScriptBuilder : SqlServerMigrationSqlGenerator
{
#if !DEBUG
protected override void Generate(SqlOperation sqlOperation)
{
Statement("GO");
base.Generate(sqlOperation);
Statement("GO");
}
public override IEnumerable<MigrationStatement> Generate(IEnumerable<MigrationOperation> migrationOperations, string providerManifestToken)
{
yield return new MigrationStatement {Sql = "BEGIN TRAN"};
foreach (var migrationStatement in base.Generate(migrationOperations, providerManifestToken))
{
yield return migrationStatement;
}
yield return new MigrationStatement {Sql = "COMMIT TRAN"};
}
#endif
}
Si dovrebbe filo che nella vostra DatabaseMigrationsConfiguration
. Esempio:
public sealed class DatabaseMigrationsConfiguration : DbMigrationsConfiguration<DatabaseContext>
{
public DatabaseMigrationsConfiguration()
{
SetSqlGenerator("System.Data.SqlClient", new MigrationScriptBuilder());
}
}
Si potrebbe prendere questo approccio, anche se noioso: http://stackoverflow.com/questions/18528376/code-first-migrations-update-database-script-command-generated-sql-script-not –