Browse Source

Update migration guide for ABP v11.0 to include .NET 11 upgrade instructions, changes to MVC UI libraries, C# client proxy generation, and updates to the Blogging module. Document necessary actions for developers regarding Owl Carousel, malihu scrollbar, and timeago.js dependencies. Also, outline changes in account management and permission checks related to user invitations and language texts.

pull/26534/head
sumeyye 2 days ago
parent
commit
c48a67878a
  1. 85
      docs/en/Blog-Posts/2026-11-19 v11_0_Release_Stable/POST.md
  2. BIN
      docs/en/Blog-Posts/2026-11-19 v11_0_Release_Stable/upgrade-abp-packages.png
  3. 101
      docs/en/release-info/migration-guides/abp-11-0.md

85
docs/en/Blog-Posts/2026-11-19 v11_0_Release_Stable/POST.md

@ -0,0 +1,85 @@
# ABP.IO Platform 11.0 Final Has Been Released!
We are glad to announce that [ABP](https://abp.io/) 11.0 stable version has been released based on [.NET 11.0](https://dotnet.microsoft.com/en-us/download/dotnet/11.0).
## What's New With Version 11.0?
All the new features were explained in detail in the [11.0 RC Announcement Post](https://abp.io/community/announcements/abp-platform-11.0-rc-has-been-released-a77t7jx8), so there is no need to review them all again. You can check it out for more details.
Here are some of the highlights of this version:
- **Upgraded to .NET 11 GA:** ABP v11.0 targets the stable .NET 11 SDK and packages (ASP.NET Core 11, EF Core 11, and MAUI 11), with Blazor startup templates adopting the `BasePath` component and updated Blazor WebAssembly host routing for .NET 11.
- **`IAsyncEnumerable<T>` support in async interceptors and C# client proxies:** Unit of work, auditing, and change tracking interceptors now run around each enumeration of `IAsyncEnumerable<T>` methods, and both dynamic and static C# client proxies can stream them.
- **Query projection for read-only application services:** Implement `IQueryProjector<TEntity, TDto>` so `GetAsync` and `GetListAsync` project queries at the database level and return only the columns required by the DTO.
- **FluentValidation rules in the API definition:** The new `Volo.Abp.Http.FluentValidation` package exposes FluentValidation constraints on the API definition alongside data annotations for client proxy generators.
- **Passkey authenticator display names:** Identity and Account Pro now store passkey AAGUIDs and infer authenticator display names (such as Windows Hello or Google Password Manager), configurable via `AbpIdentityPasskeyOptions.KnownAuthenticators`.
- **C# client proxy and localization performance improvements:** C# client proxy generation emits only contract types reachable from service signatures, static client proxy descriptions are deserialized on demand, and localization JSON dictionaries are built per requested culture.
- **Docs module modernization and library cleanup:** Docs PDF export replaces AGPL-licensed iText with `HtmlRenderer.PdfSharp` and `PDFsharp`, Docs full-text search upgrades from deprecated NEST 7 to `Elastic.Clients.Elasticsearch` 8.x, unmaintained MVC UI libraries (Owl Carousel, malihu custom scrollbar, `timeago` 1.x, `jquery-form`, and `toastr`) are replaced or removed, and `Polly` is replaced internally with `Volo.Abp.Threading.RetryHelper`.
- **Commercial module and localization updates:** Korean (`ko`) localization for commercial modules, Hebrew (`he`) localization for the framework and open-source modules, Portuguese (`pt`) Account localization, accessible password visibility toggles, CMS Kit Pro Blazor publish/draft actions, AI Management MCP session recovery, React Admin Console right-to-left (RTL) layout support, and `partial` ABP Suite generated test classes.
- **Dependency and security updates:** The final release also includes OpenIddict `7.9.0` (fixing authorization entry validation), `MongoDB.Driver` `3.14.0`, Angular `22.1`, `Devart.Data.Oracle.EFCore` `11.3.248.11`, and stability and security hardening fixes collected during the RC period.
## Getting Started with 11.0
### How to Upgrade an Existing Solution
You can upgrade your existing solutions with either ABP Studio or ABP CLI. In the following sections, both approaches are explained:
### Upgrading via ABP Studio
If you are already using the ABP Studio, you can upgrade it to the latest version. ABP Studio periodically checks for updates in the background, and when a new version of ABP Studio is available, you will be notified through a modal. Then, you can update it by confirming the opened modal. See [the documentation](https://abp.io/docs/latest/studio/installation#upgrading) for more info.
After upgrading the ABP Studio, then you can open your solution in the application, and simply click the **Upgrade ABP Packages** action button to instantly upgrade your solution:
![](upgrade-abp-packages.png)
> Please note that ABP CLI & ABP Studio only upgrade the related ABP packages, so you need to update your target framework to `net11.0` and upgrade non-ABP packages for .NET 11.0 manually.
### Upgrading via ABP CLI
Alternatively, you can upgrade your existing solution via ABP CLI. First, you need to install the ABP CLI or upgrade it to the latest version.
If you haven't installed it yet, you can run the following command:
```bash
dotnet tool install -g Volo.Abp.Studio.Cli
```
Or to update the existing CLI, you can run the following command:
```bash
dotnet tool update -g Volo.Abp.Studio.Cli
```
After installing/updating the ABP CLI, you can use the [`update` command](https://abp.io/docs/latest/CLI#update) to update all the ABP related NuGet and NPM packages in your solution as follows:
```bash
abp update
```
You can run this command in the root folder of your solution to update all ABP related packages.
> Please note that ABP CLI & ABP Studio only upgrade the related ABP packages, so you need to update your target framework to `net11.0` and upgrade non-ABP packages for .NET 11.0 manually.
## Migration Guides
This version includes breaking changes and migration-impacting updates that may affect existing applications. Key areas to review include upgrading to .NET 11, EF Core 11 database provider availability (PostgreSQL, MySQL, Pomelo, and Oracle), adding `Microsoft.EntityFrameworkCore.Design` for EF Core Tools, updating separate Blazor WebAssembly host projects, removed `Polly` and `SixLabors.ImageSharp` references, Docs module PDF (`HtmlRenderer.PdfSharp`) and Elasticsearch (`Elastic.Clients.Elasticsearch` 8.x) replacements, MVC UI library replacements, batch permission updates (`IPermissionManager`), C# client proxy generation and lazy loading, OpenIddict 7.9.0 / `Microsoft.IdentityModel.*` 8.23.0 alignment, Account Pro passkey and sign-in/extension grant constructor changes, Payment `float`-to-`decimal` conversions on .NET 11, and tightened permission checks on user invitations, language text restore, and QA organization membership.
Please read the migration guide carefully, if you are upgrading from v10.x or earlier versions: [ABP Version 11.0 Migration Guide](https://abp.io/docs/11.0/release-info/migration-guides/abp-11-0)
## Community News
### New ABP Community Articles
As always, exciting articles have been contributed by the ABP community. I will highlight some of them here:
- [QuickGrid in .NET 11: Sorting and Paging That Live in the URL](https://abp.io/community/articles/quickgrid-in-.net-11-sorting-and-paging-that-live-in-the-url-hypzmikw) by [Salih Özkara](https://abp.io/community/members/salih)
- [State Without a Circuit: TempData and Session in Blazor .NET 11 Static SSR](https://abp.io/community/articles/state-without-a-circuit-tempdata-and-session-in-blazor-.net-11-static-ssr-q8r6l6ug) by [Sümeyye Kurtuluş](https://abp.io/community/members/sumeyye.kurtulus)
- [System.Text.Json in .NET 11: Naming Policies, Union Types, and NDJSON Streaming](https://abp.io/community/articles/system.text.json-in-.net-11-naming-policies-union-types-and-ndjson-streaming-ul2reiuf) by [Okan Koca](https://abp.io/community/members/okankoca)
- [Vector and Hybrid Search with SQL Server in EF Core 11](https://abp.io/community/articles/vector-and-hybrid-search-with-sql-server-in-ef-core-11-8s06bcm7) by [Liming Ma](https://abp.io/community/members/maliming)
- [Blazor .NET 11: What's New in Virtualize, AnchorMode, and CSP Support](https://abp.io/community/articles/blazor-.net-11-whats-new-in-virtualize-anchormode-and-csp-support-hdpestha) by [Oğuzhan Ağır](https://abp.io/community/members/oguzhan.agir)
Thanks to the ABP Community for all the content they have published. You can also [post your ABP related (text or video) content](https://abp.io/community/posts/create) to the ABP Community.
## About the Next Version
The next feature version will be 11.1. You can follow the [release planning here](https://github.com/abpframework/abp/milestones). Please [submit an issue](https://github.com/abpframework/abp/issues/new) if you have any problems with this version.

BIN
docs/en/Blog-Posts/2026-11-19 v11_0_Release_Stable/upgrade-abp-packages.png

Binary file not shown.

After

Width:  |  Height:  |  Size: 16 KiB

101
docs/en/release-info/migration-guides/abp-11-0.md

@ -15,6 +15,69 @@ This document is a guide for upgrading ABP v10.x solutions to ABP v11.0. There a
This version contains the following changes on the open-source side:
### Upgrade to .NET 11
ABP v11.0 targets .NET 11. Move your solution to .NET 11 before upgrading the ABP packages. .NET 11 is a Standard Term Support release.
See [What's new in .NET 11](https://learn.microsoft.com/en-us/dotnet/core/whats-new/dotnet-11/overview) while you update the target framework and the ASP.NET Core, EF Core, and related package versions. The Blazor startup templates adopt the `BasePath` component. ABP also preserves the .NET 10 rounding behavior when `float` or `double` extra-property values are read as `decimal`.
### MVC UI Libraries
**Who is affected**
- Applications that reference `@abp/owl.carousel`, `OwlCarouselScriptContributor`, or `OwlCarouselStyleContributor`.
- Applications that reference `@abp/malihu-custom-scrollbar-plugin` or the Malihu scrollbar bundle contributors.
- Applications that call the `timeago` 1.x jQuery API directly. `@abp/timeago` now depends on `timeago.js` 4.x, and the bundled file is `/libs/timeago/timeago.full.min.js`.
- Applications that imported the `jquery-form` or `toastr` npm packages through an ABP package and do not reference them themselves.
**What changed**
- Owl Carousel is replaced by [Swiper](https://swiperjs.com/). The new packages are `@abp/swiper`, `SwiperScriptContributor`, and `SwiperStyleContributor`. `@abp/owl.carousel` and the Owl Carousel contributors are removed.
- The malihu custom scrollbar plugin is removed. The docs, feature management, and permission management pages use the browser scrollbar.
- `@abp/timeago` still contributes `TimeagoScriptContributor` and `abp.timeago.js`, and it loads `timeago.js` instead of the unmaintained `timeago` 1.x package.
- The unused `jquery-form` and `toastr` npm packages are no longer brought in by ABP. ABP toast notifications stay on ABP's own implementation.
**What to do**
- Replace Owl Carousel markup and initialization with Swiper if your pages called the Owl Carousel API.
- Remove malihu scrollbar initialization and any bundle contributor references.
- Review custom `timeago` calls against the [timeago.js](https://github.com/hustcc/timeago.js) 4.x API.
- Add your own `jquery-form` or `toastr` package reference if your pages still load those libraries.
> See [#26005](https://github.com/abpframework/abp/pull/26005), [#26000](https://github.com/abpframework/abp/pull/26000), [#26001](https://github.com/abpframework/abp/pull/26001), and [#26002](https://github.com/abpframework/abp/pull/26002).
### C# Client Proxies Generate Only Used Types
**Who is affected**
- Applications that regenerate C# client proxies and compile against generated contract types that are not reachable from an application service signature.
**What changed**
`CSharpServiceProxyGenerator` generates only the contract types reachable from service signatures. Types that are already referenced from the client project's assets are not generated again. Nested, generic, and same-named types that appear in signatures are still generated.
**What to do**
Reference the contract package, or keep a local type, for any DTO you use that the generator no longer emits. Regenerate the proxies after upgrading.
> See [#26205](https://github.com/abpframework/abp/pull/26205) for details.
### Blogging Module Uses SkiaSharp
**Who is affected**
- Applications that use SixLabors.ImageSharp in their own code without referencing it themselves, and get it through the Blogging module.
**What changed**
The Blogging module detects uploaded image formats with SkiaSharp (`SKCodec`) and no longer references `SixLabors.ImageSharp`.
**What to do**
Reference `SixLabors.ImageSharp` in the projects that use it.
> See [#26264](https://github.com/abpframework/abp/pull/26264) for details.
### Batch Permission Update
**Who is affected**
@ -24,7 +87,7 @@ This version contains the following changes on the open-source side:
**What changed**
- `IPermissionManager` has a new `SetAsync(IEnumerable<KeyValuePair<string, bool>>, string, string)` member. It reads the current state of every requested permission once and writes only the permissions whose state changes, instead of querying the current state once per permission.
- `IPermissionManager` has a new `SetAsync(IEnumerable<KeyValuePair<string, bool>>, string, string)` member. It checks permission grants in a batch and updates only the permissions whose state changes.
- `PermissionAppService.UpdateAsync` calls the new overload once instead of calling the single-permission `SetAsync` in a loop. A derived `PermissionManager` that only overrides the single-permission overload still compiles, but the permission management UI no longer goes through it.
**What to do**
@ -141,7 +204,7 @@ ABP will remove these workarounds once the SDK fixes the problems.
| Volo.Abp.SettingManagement.Domain | Polly |
- The number of attempts, the delays between them and the failures that are retried are unchanged in all of them.
- No ABP API takes or returns a Polly type, so nothing else changes for an application that does not use Polly itself.
- File-system operations now also observe cancellation before an attempt and while waiting between attempts.
**What to do**
@ -369,3 +432,37 @@ decimal totalPrice = PaymentAmountHelper.ToDecimal(product.TotalPrice);
```
The helper rounds to seven significant digits, rather than a fixed number of decimal places. For your own decimal constants, use a decimal literal such as `19.99m` instead of `(decimal)19.99f`.
### Account Pro, Extension Grants, and Elsa Identity Sign-In Checks
**Who is affected**
- Applications that derive from or construct `Volo.Abp.Account.Public.Web.Areas.Account.Controllers.AccountController`, `LinkLoginExtensionGrantValidator`, or `SwitchTenantExtensionGrantValidator`.
- Applications that customize `AbpIdentityUserCredentialsValidator` or `AbpIdentityAccessTokenIssuer` in `Volo.Abp.Elsa.Identity`.
**What changed**
- Account pages/controllers, link login, impersonation, tenant switch grants, and Elsa Identity login now perform `AbpSignInManager` sign-in checks before signing a user in.
- `AccountController` adds an `AbpSignInManager` constructor parameter.
- `LinkLoginExtensionGrantValidator` and `SwitchTenantExtensionGrantValidator` add `AbpSignInManager` and `IOptions<IdentityOptions>` constructor parameters.
- `Volo.Abp.Elsa.Identity` now depends on `Volo.Abp.Identity.AspNetCore`. `AbpIdentityUserCredentialsValidator` returns only the user ID and takes `AbpIdentityUserSignInChecker`, `IdentitySecurityLogManager`, and `IUnitOfWorkManager` (replacing `ITenantStore`), and `AbpIdentityAccessTokenIssuer` no longer issues a refresh token.
**What to do**
Update constructors in any derived classes to pass the new dependencies to the base constructor, and review any custom Elsa Identity credential or token issuance code if you relied on refresh tokens or the previous validator signature. (This change was also shipped in v10.7.1; no additional change is needed if you already migrated for v10.7.1.)
### Permission Checks on User Invitations, Language Texts, and QA Organizations
**Who is affected**
- Applications whose roles or clients call user invitation endpoints, `LanguageTextAppService.RestoreToDefaultAsync`, or QA organization membership operations without the corresponding permissions.
**What changed**
- User invitation endpoints in `IdentityUserAppService` now require `AbpIdentity.Users.Create`. Pre-assigned roles follow the same assignment restrictions as user creation: `AbpIdentity.Users.ManageRoles` is required, and non-admin users can only assign their own roles.
- `LanguageTextAppService.RestoreToDefaultAsync` now requires `LanguageManagement.LanguageTexts.Edit`.
- QA organization member changes (including members added via `AdminOrganizationAppService.CreateAsync`) now require the `Organizations.AddMember` / `Organizations.RemoveMember` permissions.
**What to do**
Ensure roles and API clients that perform these operations have the required permissions granted.

Loading…
Cancel
Save