Browse Source

Merge pull request #12563 from abpframework/EngincanV/migration-guide

Create Migration Guide for v5.3
pull/12565/head
Enis Necipoglu 4 years ago
committed by GitHub
parent
commit
58cbcf029f
No known key found for this signature in database GPG Key ID: 4AEE18F83AFDEB23
  1. 7
      docs/en/Migration-Guides/Abp-5_3.md
  2. 1
      docs/en/Migration-Guides/Index.md

7
docs/en/Migration-Guides/Abp-5_3.md

@ -0,0 +1,7 @@
# ABP Version 5.3 Migration Guide
This document is a guide for upgrading ABP v5.2 solutions to ABP v5.3. There is a change in this version that may effect your applications, please read it carefully and apply the necessary changes to your application.
## AutoMapper Upgraded to v11.0.1
AutoMapper library upgraded to **v11.0.1** in this version. So, you need to change your project's target SDK that use the **AutoMapper** library (typically your `*.Application` project). You can change it from `netstandard2.0` to `netstandard2.1` or `net6` if needed. Please see [#12189](https://github.com/abpframework/abp/pull/12189) for more info.

1
docs/en/Migration-Guides/Index.md

@ -2,6 +2,7 @@
The following documents explain how to migrate your existing ABP applications. We write migration documents only if you need to take an action while upgrading your solution. Otherwise, you can easily upgrade your solution using the [abp update command](../Upgrading.md).
- [5.2 to 5.3](Abp-5_3.md)
- [5.1 to 5.2](Abp-5_2.md)
- [4.x to 5.0](Abp-5_0.md)
- [4.2 to 4.3](Abp-4_3.md)

Loading…
Cancel
Save