I have an issue where we are using EF 4.3 Code First against an existing database. I want to use the Mini-Profiler with EF and call
MvcMiniProfiler.MiniPro
I found additional "hack" issue for disabling EntityFramework database initialization (if not required). DefaultInitializer for DB should be set to null before initializing db contexts and MiniProfiler
Type type = typeof(DbContext).Assembly.GetType("System.Data.Entity.Internal.LazyInternalContext");
var field = type.GetField("DefaultCodeFirstInitializer", BindingFlags.NonPublic | BindingFlags.Static);
if (field != null)
field.SetValue(null, null);
else
{
var field2 = type.GetField("_defaultCodeFirstInitializer", BindingFlags.NonPublic | BindingFlags.Static);
if (field2 != null)
field2.SetValue(null, null);
}
So, it will resolve problems with dbo.EdmMetadata and dbo.__MigrationHistory tables