MVC操作SQL数据库：递增实体表后ConnectionString未初始化报错求助

Hey there, let's dig into this The ConnectionString property has not been initialized error you're hitting. It's tricky that it only pops up after the entity table increment works—so the issue is almost certainly tied to how you're handling the connection for your non-entity table insert. Here are the most common causes and fixes to check:

1. Your non-entity table operation lacks a properly initialized connection #

If you're using ADO.NET directly for the non-entity table insert (instead of Entity Framework), it's easy to forget to set the connection string on your SqlConnection object.

Wrong: #

// Missing connection string assignment
using (var conn = new SqlConnection())
{
    conn.Open(); // This will throw the error
    // Insert logic here
}

Right: #

Grab the connection string from your config file and pass it to the SqlConnection constructor:

// For .NET Framework (web.config)
var connString = ConfigurationManager.ConnectionStrings["YourDbConnection"].ConnectionString;

// For .NET Core (appsettings.json)
// var connString = _configuration.GetConnectionString("YourDbConnection");

using (var conn = new SqlConnection(connString))
{
    conn.Open();
    // Execute your INSERT command here
    var insertCmd = new SqlCommand("INSERT INTO NonEntityTable (Column1, Column2) VALUES (@val1, @val2)", conn);
    insertCmd.Parameters.AddWithValue("@val1", "YourValue1");
    insertCmd.Parameters.AddWithValue("@val2", "YourValue2");
    insertCmd.ExecuteNonQuery();
}

2. You're reusing a disposed Entity Framework context #

If you're using EF for both operations, make sure you're not trying to use a context that's already been disposed (e.g., from a using block that wrapped the increment operation).

Wrong: #

using (var context = new YourDbContext())
{
    // Increment entity table logic
    var entity = context.YourEntities.Find(1);
    entity.Counter++;
    context.SaveChanges();
}

// Trying to use the same disposed context for non-entity insert
context.Database.ExecuteSqlCommand("INSERT INTO NonEntityTable (...) VALUES (...)"); // Error here

Right: #

Create a new context instance for the second operation, or keep the context alive for both steps:

// Option 1: Reuse the same context for both operations
using (var context = new YourDbContext())
{
    // Increment entity table
    var entity = context.YourEntities.Find(1);
    entity.Counter++;
    context.SaveChanges();

    // Insert to non-entity table using the same context
    context.Database.ExecuteSqlCommand("INSERT INTO NonEntityTable (Column1) VALUES (@val)", new SqlParameter("@val", "Test"));
}

// Option 2: Create a new context for the second operation
using (var context = new YourDbContext())
{
    // Increment logic...
    context.SaveChanges();
}

using (var newContext = new YourDbContext())
{
    newContext.Database.ExecuteSqlCommand("INSERT INTO NonEntityTable (...) VALUES (...)");
}

3. Mismatched connection string name in config #

Double-check that the connection string name you're referencing in code matches exactly what's in your config file.

For .NET Framework (web.config): #

<connectionStrings>
    <!-- Make sure "YourDbConnection" matches what you use in code -->
    <add name="YourDbConnection" 
         connectionString="Data Source=YOUR_SERVER;Initial Catalog=YOUR_DB;Integrated Security=True;" 
         providerName="System.Data.SqlClient" />
</connectionStrings>

For .NET Core (appsettings.json): #

"ConnectionStrings": {
    // Ensure this name matches your code reference
    "YourDbConnection": "Server=YOUR_SERVER;Database=YOUR_DB;Trusted_Connection=True;"
}

4. Async/await issues (if using async operations) #

If you're using async methods, make sure you're properly awaiting every asynchronous call. Failing to do so can cause contexts or connections to be disposed prematurely.

Wrong: #

// Missing await - context might be disposed before insert completes
context.SaveChangesAsync();
context.Database.ExecuteSqlCommandAsync("INSERT INTO NonEntityTable (...) VALUES (...)");

Right: #

await context.SaveChangesAsync();
await context.Database.ExecuteSqlCommandAsync("INSERT INTO NonEntityTable (...) VALUES (...)");

If you can share snippets of your controller code (specifically the increment and insert logic) and your connection string config, we can pinpoint the exact issue even faster!

内容的提问来源于stack exchange，提问作者tCoe