Browse Source

Update ABP 10.0 migration guide for OpenIddict and Mapperly

pull/23609/head
maliming 1 year ago
parent
commit
8af63bc3db
No known key found for this signature in database GPG Key ID: A646B9CB645ECEA4
  1. 12
      docs/en/release-info/migration-guides/abp-10-0.md

12
docs/en/release-info/migration-guides/abp-10-0.md

@ -51,6 +51,18 @@ M((array, num) => Enumerable.Contains(array, num)); // ok, binds to Enumerable.C
See the [C# 14 overload resolution with span parameters](https://learn.microsoft.com/en-us/dotnet/core/compatibility/core-libraries/10.0/csharp-overload-resolution#recommended-action) for more information.
### OpenIddict 7.X
We upgraded OpenIddict to 7.X. See the [OpenIddict 6.x to 7.x Migration Guide](https://documentation.openiddict.com/guides/migration/60-to-70.html) for more information.
OpenIddict 7.X changed the `OpenIddictToken` entity, you must create a new database migration if you use Entity Framework Core.
### Migrating from AutoMapper to Mapperly
The AutoMapper library is no longer free for commercial use. For more details, you can refer to this [announcement post](https://www.jimmybogard.com/automapper-and-mediatr-going-commercial/).
In this version, all ABP modules use Mapperly instead of AutoMapper. ABP Framework provides both AutoMapper and Mapperly integrations. If your project currently uses AutoMapper and you don't have a commercial license, you can follow the [Migrating from AutoMapper to Mapperly](https://github.com/abpframework/abp/blob/dev/docs/en/release-info/migration-guides/AutoMapper-To-Mapperly.md) document to migrate to Mapperly.
### Failure Retry Policy for InboxProcessor
We added a failure retry policy to `AbpEventBusBoxesOptions` (see `InboxProcessorFailurePolicy` and `InboxProcessorRetryBackoffFactor`). Because this change adds and removes fields in the `IncomingEventRecord` entity, you must create a new database migration if you use Inbox/Outbox with Entity Framework Core.

Loading…
Cancel
Save