We got this bug report from Fitzchack Yitzchaki of Hibernating Rhinos:
public class SqlServerMigrationSqlGenerator : MigrationSqlGenerator
{
protected virtual DbConnection CreateConnection()
{
return new SqlConnection();
}
Instead of hard codding the connection, we expecting it to use:
public class ProfiledMigrationSqlGenerator : SqlServerMigrationSqlGenerator
{
protected override DbConnection CreateConnection()
{
return DbProviderFactories.GetFactory("System.Data.SqlClient").CreateConnection();
}
So we can actually turn it to ProfiledConnection. This is how you did this in SqlCeMigrationSqlGenerator:
public class SqlCeMigrationSqlGenerator : SqlServerMigrationSqlGenerator { /// <inheritdoc /> protected override DbConnection CreateConnection() { return DbProviderFactories.GetFactory("System.Data.SqlServerCe.4.0").CreateConnection(); }
public class SqlServerMigrationSqlGenerator : MigrationSqlGenerator
{
protected virtual DbConnection CreateConnection()
{
return new SqlConnection();
}
Instead of hard codding the connection, we expecting it to use:
public class ProfiledMigrationSqlGenerator : SqlServerMigrationSqlGenerator
{
protected override DbConnection CreateConnection()
{
return DbProviderFactories.GetFactory("System.Data.SqlClient").CreateConnection();
}
So we can actually turn it to ProfiledConnection. This is how you did this in SqlCeMigrationSqlGenerator:
public class SqlCeMigrationSqlGenerator : SqlServerMigrationSqlGenerator { /// <inheritdoc /> protected override DbConnection CreateConnection() { return DbProviderFactories.GetFactory("System.Data.SqlServerCe.4.0").CreateConnection(); }