EF Core执行add-migration时出现STA线程错误及Microsoft.Extensions.Hosting服务访问异常的原因排查

Hey there, let's unpack this issue you're facing. That STA thread error popping up after updating Visual Studio and NuGet packages is almost always tied to a compatibility quirk between the newer VS tooling and how EF Core's design-time tools run migrations. Here's the breakdown:

Root Causes #

• VS 17.3+ Tooling Changes: Visual Studio 17.3.x introduced updates to how it handles design-time operations for .NET projects. EF Core's add-migration command runs in a background thread, which defaults to MTA (Multi-Threaded Apartment) mode. However, some updated components (either in EF Core Tools or dependent NuGet packages) now inadvertently try to access UI-related functionality that requires an STA (Single-Threaded Apartment) thread.
• NuGet Package Conflicts: When you updated your NuGet packages (especially Microsoft.EntityFrameworkCore.Tools or PostgreSQL EF Core provider packages), you might have pulled in a version that has new dependencies requiring STA thread context—something that wasn't present in older versions where migrations worked fine.
• Accidental UI Dependencies: It's also possible that one of your updated packages (even unrelated ones) introduced a hidden dependency on WinForms/WPF components, which enforce STA thread requirements even in non-UI projects during design-time operations.

Fixes to Try #

1. Force STA Thread Mode with a Design-Time Context Factory #

The most reliable fix is to create a custom design-time factory for your DataContext that explicitly sets the thread to STA mode before initializing the context. Here's how to do it:

Add this class to your project (make sure it's in the same namespace as your DataContext):

using Microsoft.EntityFrameworkCore;
using Microsoft.EntityFrameworkCore.Design;
using System.Threading;

namespace YourProjectNamespace
{
    public class DataContextDesignTimeFactory : IDesignTimeDbContextFactory<YourDataContext>
    {
        public YourDataContext CreateDbContext(string[] args)
        {
            // Set the current thread to STA mode to satisfy UI component requirements
            Thread.CurrentThread.SetApartmentState(ApartmentState.STA);

            var optionsBuilder = new DbContextOptionsBuilder<YourDataContext>();
            // Replace with your actual connection string (you can also load it from config if needed)
            optionsBuilder.UseNpgsql("YourPostgreSQLConnectionString");

            return new YourDataContext(optionsBuilder.Options);
        }
    }
}

Once this is in place, EF Core will use this factory during migrations, ensuring the thread is STA-compliant.

2. Roll Back EF Core Tools to a Compatible Version #

If the custom factory feels like overkill, try rolling back Microsoft.EntityFrameworkCore.Tools to a version that worked before your VS update. For example, if you updated to 6.0.10 or later, downgrade to 6.0.9—this version doesn't have the STA thread conflict with VS 17.3.5.

You can do this via the NuGet Package Manager, or run this command in the Package Manager Console:

Install-Package Microsoft.EntityFrameworkCore.Tools -Version 6.0.9

3. Check for Unintended UI Dependencies #

Double-check your NuGet packages to make sure you didn't accidentally install WinForms/WPF-related packages in your data access project. For example, if you see System.Windows.Forms or PresentationFramework listed, remove them—they're likely the source of the STA requirement.

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