From aa33fdc87848facaa62c1e49c216fbb10944b163 Mon Sep 17 00:00:00 2001 From: liangshiwei Date: Fri, 13 Oct 2023 13:38:16 +0800 Subject: [PATCH 1/2] Add Blazor UI section --- docs/en/Migration-Guides/Abp-7_4.md | 22 +++++++++++++++------- 1 file changed, 15 insertions(+), 7 deletions(-) diff --git a/docs/en/Migration-Guides/Abp-7_4.md b/docs/en/Migration-Guides/Abp-7_4.md index b2996d0a0a..bc3243fb63 100644 --- a/docs/en/Migration-Guides/Abp-7_4.md +++ b/docs/en/Migration-Guides/Abp-7_4.md @@ -8,13 +8,6 @@ In this version, the `Microsoft.Extensions.FileProviders.Embedded` (and other `M > You can check [this issue](https://github.com/abpframework/abp/pull/17516) to see the updated package versions. -## Bumped the `Blazorise` dependencies to `1.3.1` -In this version, the `Blazorise` dependencies are upgraded to `1.3.1` version. So, if your solution includes any **Blazor** project, then you should upgrade Blazorise packages to 1.3.1 in your `Blazor.csproj` file. -The following packages are included in the templates by default: -- `Blazorise.Bootstrap5` -- `Blazorise.Icons.FontAwesome` -> _If your project depends on more blazorise packages, then you should upgrade all of them._ - ## Renamed the `AddGlobalFilters<>` method as `FilterQueryable<>` in `IMongoDbRepositoryFilterer` ABP Framework provides services to automatically filter data on querying from a database. Prior to this version, creating a new class that derives from the `MongoDbRepositoryFilterer` and overriding its `AddGlobalFilters` method was needed for implementing a data filter for [MongoDB](../MongoDB.md). @@ -105,3 +98,18 @@ Configure(options => options.ExposeIntegrationServices = true; }); ``` + +## Blazor UI +If you use Blazor WASM or Blazor Server UI, you should follow this section. + +### Bumped the `Blazorise` dependencies to `1.3.1` +In this version, the `Blazorise` dependencies are upgraded to `1.3.1` version. you should upgrade Blazorise packages to `1.3.1` in your `Blazor.csproj` file. +The following packages are included in the templates by default: +- `Blazorise.Bootstrap5` +- `Blazorise.Icons.FontAwesome` +- `Blazorise.Components` +> _If your project depends on more blazorise packages, then you should upgrade all of them._ +> You should execute `dotnet build` & `abp bundle` commands in the Blazor project if you are using the Blazor WebAssembly. + +### Bumped the `Microsoft.AspNetCore.Components.*` dependency to `7.0.10` +In this version, the `Microsoft.AspNetCore.Components.*` dependencies are upgraded to `7.0.10` version. you should upgrade `Microsoft.AspNetCore.Components.Web` and `Microsoft.AspNetCore.Components.WebAssembly` packages to `7.0.10` in your `Blazor.csproj` file. From 2b46734d471be31e163730fdfcb679a829a7fe95 Mon Sep 17 00:00:00 2001 From: Engincan VESKE Date: Mon, 16 Oct 2023 09:23:53 +0300 Subject: [PATCH 2/2] Update Abp-7_4.md --- docs/en/Migration-Guides/Abp-7_4.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/en/Migration-Guides/Abp-7_4.md b/docs/en/Migration-Guides/Abp-7_4.md index bc3243fb63..0c69dda74e 100644 --- a/docs/en/Migration-Guides/Abp-7_4.md +++ b/docs/en/Migration-Guides/Abp-7_4.md @@ -87,7 +87,7 @@ In this version, ABP Framework introduces the `IdentityUserIntegrationService`, This is a breaking change for microservice solutions because of the following two reasons and it should be considered: -* `IdentityUserIntegrationService` provides non-authorized services. This is not breaking the application, but should be taken care of. Since, everyone can use the service to retrieve some information for a certain user (for example, the role names of a user). +* `IdentityUserIntegrationService` provides non-authorized services. This is not breaking the application but should be taken care of. Since, everyone can use the service to retrieve some information for a certain user (for example, the role names of a user). * Secondly, since integration services are not exposed by default anymore as explained in the *Exposing Integration Services* section above, you should explicitly enable exposing integration services. Otherwise, the operation will fail and you'll get a `404` error from the identity microservice. To expose integration services and controllers, you can configure the `AbpAspNetCoreMvcOptions` and set the `ExposeIntegrationServices` property as *true* in the `ConfigureServices` method of your [module class](../Module-Development-Basics.md): @@ -103,7 +103,7 @@ Configure(options => If you use Blazor WASM or Blazor Server UI, you should follow this section. ### Bumped the `Blazorise` dependencies to `1.3.1` -In this version, the `Blazorise` dependencies are upgraded to `1.3.1` version. you should upgrade Blazorise packages to `1.3.1` in your `Blazor.csproj` file. +In this version, the `Blazorise` dependencies are upgraded to the `1.3.1` version. you should upgrade Blazorise packages to `1.3.1` in your `Blazor.csproj` file. The following packages are included in the templates by default: - `Blazorise.Bootstrap5` - `Blazorise.Icons.FontAwesome` @@ -112,4 +112,5 @@ The following packages are included in the templates by default: > You should execute `dotnet build` & `abp bundle` commands in the Blazor project if you are using the Blazor WebAssembly. ### Bumped the `Microsoft.AspNetCore.Components.*` dependency to `7.0.10` -In this version, the `Microsoft.AspNetCore.Components.*` dependencies are upgraded to `7.0.10` version. you should upgrade `Microsoft.AspNetCore.Components.Web` and `Microsoft.AspNetCore.Components.WebAssembly` packages to `7.0.10` in your `Blazor.csproj` file. + +In this version, the `Microsoft.AspNetCore.Components.*` dependencies are upgraded to the `7.0.10` version. Therefore, you should upgrade the `Microsoft.AspNetCore.Components.Web` and `Microsoft.AspNetCore.Components.WebAssembly` packages to `7.0.10` in your `Blazor.csproj` file.