ABP版本升级求助：无法获取支持EntityHistory的高版本问题

Alright, let's tackle this issue you're having with ASP.NET Boilerplate (ABP) and enabling entity history tracking. Here's a breakdown of what's blocking you and how to resolve it:

Why Can't You Upgrade Beyond v2.3.0? #

The most common reason you're stuck at ABP v2.3.0 is a low target framework version in your project. ABP v3.0.0 (the first version that introduced the Configuration.EntityHistory.IsEnabled setting) requires at least .NET Framework 4.6.1. If your project is targeting an older framework like 4.5 or 4.6, NuGet will hide newer ABP packages that aren't compatible.

Step-by-Step Solution to Upgrade & Enable Entity History #

1. Upgrade Your Project's Target Framework #

First, you need to bump your project's target framework to meet ABP v3.0.0+'s requirements:

• Right-click your project in Visual Studio → Properties → Go to the Application tab.
• Under Target framework, select .NET Framework 4.6.1 or higher (4.7.2 is recommended for better compatibility).
• Save changes and rebuild your project.

2. Clear NuGet Cache (to See Newer Packages) #

Sometimes cached NuGet data can prevent you from seeing the latest available package versions. Clear it like this:

• Go to Tools → NuGet Package Manager → Package Manager Settings.
• Navigate to NuGet Package Manager → General → Click Clear All NuGet Cache(s).
• Confirm the action and wait for the cache to clear.

3. Upgrade ABP Packages to v3.0.0+ #

Now you should be able to upgrade to ABP versions that support entity history:

• Open the NuGet Package Manager Console or use the Manage NuGet Packages UI.
• Upgrade the core Abp package first, then update all dependent ABP packages (like Abp.Web.Mvc, Abp.EntityFramework, etc.) to the same version. Make sure all ABP packages are on the same version to avoid compatibility issues.

4. Enable Entity History in Your Module #

Once upgraded, you can finally configure entity history in your module's PreInitialize() method:

public override void PreInitialize()
{
    // Enable global entity history tracking
    Configuration.EntityHistory.IsEnabled = true;

    // Optional: Track only specific entities (e.g., entities implementing a custom interface)
    Configuration.EntityHistory.Selectors.Add(
        new NamedTypeSelector("CustomEntities", type => typeof(IMyTrackableEntity).IsAssignableFrom(type))
    );
}

5. Update Your Database #

Enabling entity history adds new tables to your database (like EntityChangeSets and EntityChanges). You'll need to generate and apply Entity Framework migrations:

• In the Package Manager Console, run Add-Migration AddedEntityHistoryTables to create a new migration.
• Run Update-Database to apply the migration to your database.

If You Can't Upgrade to v3.0.0+ (Alternative) #

If for some reason you can't upgrade your target framework, you can implement a basic custom entity tracker:

• Use ABP's built-in domain events (e.g., EntityCreatedEventData<T>, EntityUpdatedEventData<T>) to hook into entity changes.
• Create a custom repository to log changes, user information, and timestamps into a dedicated audit table. This is more manual but works if you're stuck on older ABP versions.

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