自数据库创建以来，支持<Database>上下文的模型已经更改

错误信息:

“自数据库创建以来，支持‘AddressBook’上下文的模型已经发生了变化。手动删除/更新数据库，或者调用database。带有IDatabaseInitializer实例的SetInitializer。例如，RecreateDatabaseIfModelChanges策略将自动删除并重新创建数据库，并可选地为其添加新数据。”

我正在尝试使用代码优先功能，以下是我写的:

var modelBuilder = new ModelBuilder();
var model = modelBuilder.CreateModel();
using (AddressBook context = new AddressBook(model))
{
    var contact = new Contact
    {
        ContactID = 10000,
        FirstName = "Brian",
        LastName = "Lara",
        ModifiedDate = DateTime.Now,
        AddDate = DateTime.Now,
        Title = "Mr."

    };
    context.contacts.Add(contact);
    int result = context.SaveChanges();
    Console.WriteLine("Result :- "+ result.ToString());
}

上下文类:

public class AddressBook : DbContext
{
    public AddressBook()
    { }
    public AddressBook(DbModel AddressBook)
        : base(AddressBook)
    {

    }
    public DbSet<Contact> contacts { get; set; }
    public DbSet<Address> Addresses { get; set; }
}

和连接字符串:

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
    <connectionStrings>
    <add name="AddressBook" providerName="System.Data.SqlClient"  
         connectionString="Data Source=MyMachine;Initial Catalog=AddressBook;
         Integrated Security=True;MultipleActiveResultSets=True;"/>
    </connectionStrings>
</configuration>

因此，数据库名称是“AddressBook”，当我试图将联系人对象添加到上下文时发生错误。我遗漏了什么吗?

当前回答

我有这个问题，原来是一个项目指向SQLExpress，但有问题的是指向LocalDb。(在它们各自的web.config中)。愚蠢的疏忽，但值得注意的是，如果其他人正在排除这个问题。

2014-01-02 00:18:50

其他回答

这意味着上下文上的一些更改还没有执行。请先运行Add-Migration来生成我们所做的更改(我们可能没有意识到的更改) 然后运行Update-Database

2015-08-22 08:07:48

刚刚找到答案，想在这里更新。只需要做以下事情。

public class AddressBook: DbContext
{
   protected override void OnModelCreating(ModelBuilder modelBuilder)
   {
    modelBuilder.IncludeMetadataInDatabase = false;
   }
}

2010-08-30 12:47:13

检查以下步骤

Database.SetInitializer(空);——> Global.asax.cs

你的Context类名应该与之匹配检查它

2014-02-03 11:10:58

I had the same issue - re-adding the migration and updating the database didn't work and none of the answers above seemed right. Then inspiration hit me - I'm using multiple tiers (one web, one data, and one business). The data layer has the context and all the models. The web layer never threw this exception - it was the business layer (which I set as console application for testing and debugging). Turns out the business layer wasn't using the right connection string to get the db and make the context. So I added the connection string to the app config of the business layer (and the data layer) and viola it works. Putting this here for others who may encounter the same issue.

2016-09-30 19:02:15

创建自定义上下文初始化项:

public class MyDbContextInitializer : MigrateDatabaseToLatestVersion<MyDbContext, Migrations.Configuration>
{
    public override void InitializeDatabase(MyDbContext context)
    {
        bool exists = context.Database.Exists();

        base.InitializeDatabase(context);

        if (!exists)
        {         
            MyDbSeed.Seed(context);
        }
    }       
}

注意迁移。Configuration是Package Manager Console中由迁移命令行生成的类。您可能需要将迁移的内部修饰符更改为公共修饰符。配置类。

并从您的OmModelCreating注册它:

public partial class MyDbContext : DbContext
{

    protected override void OnModelCreating(DbModelBuilder modelBuilder)
    {
        Database.SetInitializer<MyDbContext>(new MyDbContextInitializer());

        //other code for creating model
    }
}

2018-07-23 12:38:50

自数据库创建以来，支持<Database>上下文的模型已经更改

推荐文章

最新文章

标签