Description: We are encountering runtime errors after upgrading Blazorise to 2.0.2 in an ABP 10.1.1 (Pro) application. Despite following the official migration guide ABP Blazorise 1.x to 2.0 Migration Guide, ABP Pro Blazor modules appear to still depend on Blazorise 1.8.x, causing type resolution failures at runtime.
Exception message and full stack trace
Could not load type 'Blazorise.TextEdit' from assembly 'Blazorise, Version=2.0.2.0, Culture=neutral, PublicKeyToken=null'. at Volo.Abp.Identity.Pro.Blazor.Pages.Identity.OrganizationUnitsManagement.HLIlKKXmTc(RenderTreeBuilder ) at Volo.Abp.Identity.Pro.Blazor.Pages.Identity.OrganizationUnitsManagement.HLIlKKXmTc(RenderTreeBuilder ) at Microsoft.AspNetCore.Components.Rendering.RenderTreeBuilder.AddContent(Int32 sequence, RenderFragment fragment) at Blazorise.Bootstrap5.Components.Field.<BuildRenderTree>b__1_0(RenderTreeBuilder __builder2) at Microsoft.AspNetCore.Components.CascadingValue1.Render(RenderTreeBuilder builder) at Microsoft.AspNetCore.Components.Rendering.ComponentState.RenderIntoBatch(RenderBatchBuilder batchBuilder, RenderFragment renderFragment, Exception& renderFragmentException)Steps to reproduce the issue:
- Start with ABP 10.1.1 (Blazor Server, Pro template)
- Upgrade Blazorise packages to 2.0.2
- Run the application
- Navigate to Pro module pages (e.g., Identity → Organization Units)
- Observed Behavior
- Runtime exceptions occur when rendering ABP Pro Blazor components
- Errors indicate missing types like Blazorise.TextEdit
- Multiple UI components fail due to type mismatches
- Analysis
- ABP Pro packages (e.g., Volo.Abp.Identity.Pro.Blazor) are compiled against Blazorise 1.8.x
- NuGet dependency graph confirms mixed versions:
- Blazorise (2.0.2) (project reference)
- Blazorise.Components (1.8.8) (transitive via ABP)
- Question
- Is Blazorise 2.x officially supported in ABP 10.1.1 (especially Pro modules)?
- If not, what is the recommended compatible version?
- Is there a timeline for full Blazorise 2.x support?
Need a fast resolution for this.
2 Answer(s)
-
0
ABP 10.1.1 (including ABP Commercial/Pro Blazor modules) is not compatible with Blazorise 2.x.
Your exception is the expected runtime failure mode when you force Blazorise 2.x into an ABP version whose UI modules were built against Blazorise 1.8.x APIs (e.g.,Blazorise.TextEditwas changed/removed in v2, so ABP Pro components compiled against v1 types will fail at runtime withCould not load type ...).Fast resolution (recommended for ABP 10.1.1):
- Downgrade Blazorise packages back to the Blazorise 1.8.x line (keep versions aligned across all Blazorise-* packages: Blazorise, Blazorise.Bootstrap5, Blazorise.Icons.*, Blazorise.Components, etc.).
- Remove any explicit
2.0.2references so ABP’s transitive dependencies are not overridden by your project. - Clean/rebuild (and if you use ABP CLI, run
abp clean) to ensure old assemblies aren’t lingering.
When is Blazorise 2.x supported?
- ABP upgrades Blazorise to 2.0 starting with ABP 10.2. So the correct path to use Blazorise 2.x with ABP Pro modules is to upgrade your whole solution (and all ABP Commercial packages) to ABP 10.2+, then follow the Blazorise 2.0 migration steps.
Timeline
- The only verified info available is that Blazorise 2.0 support is delivered in ABP 10.2. No verified statement is available in the provided sources for a more specific “timeline” beyond that.
Links (verified):
- https://abp.io/community/articles/05zatjfq (ABP 10.2 RC release notes: “Blazor: Upgrade to Blazorise 2.0”)
- https://abp.io/docs/10.2/release-info/migration-guides/blazorise-2-0-migration
This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.
-
0
Thank you for reporting this.
Blazorise 2.x is not supported in ABP 10.1.x. The Pro Blazor packages in 10.1.x were compiled against Blazorise 1.8.x, so upgrading Blazorise independently to 2.0.x will cause the runtime type load exceptions you are seeing (
TextEditwas renamed toTextInputin Blazorise 2.0, among other breaking changes).Blazorise 2.0 support is included in ABP 10.2, which is currently at RC stage. Please upgrade to ABP 10.2 once it is officially released to use Blazorise 2.0.
In the meantime, please downgrade Blazorise back to 1.8.x when using ABP 10.1.x.
Thanks.
