Blazorise "free version" banner: ABP forces Blazorise >= 1.8.6

[omer-repo]

Problem

Starting from Blazorise 1.8.3+, Blazorise shows a persistent footer message in the UI:

"Thank you for using the free version of the Blazorise component library! ..."

This is disruptive for production apps and affects UI/branding.

ABP support suggested downgrading Blazorise packages to 1.8.1 in some cases (e.g.):
https://abp.io/support/questions/9896/Unwanted-Blazorise-Message-Appearing-After-ABP-and-Blazorise-Update

However, after upgrading to ABP 10.0.1, we cannot downgrade Blazorise to 1.8.1 because ABP enforces a newer Blazorise version via transitive dependencies.

Current ABP version

ABP: 10.0.1 (community / open-source)
UI: Blazor (WASM, but likely affects other Blazor modes too)

What happens when trying to downgrade

We tried to pin Blazorise packages to 1.8.1 (or 1.8.0) in MyCompany.MyProject.Blazor.Client but NuGet fails with a package downgrade warning-as-error:

Warning As Error: Detected package downgrade: Blazorise from 1.8.6 to 1.8.0. MyCompany.MyProject.Blazor.Client -> Volo.Abp.SettingManagement.Blazor.WebAssembly 10.0.1 -> Volo.Abp.AspNetCore.Components.WebAssembly.Theming 10.0.1 -> Volo.Abp.AspNetCore.Components.Web.Theming 10.0.1 -> Volo.Abp.BlazoriseUI 10.0.1 -> Blazorise (>= 1.8.6) MyCompany.MyProject.Blazor.Client -> Blazorise (>= 1.8.0)

So effectively, Volo.Abp.BlazoriseUI requires Blazorise (>= 1.8.6) and prevents us from using 1.8.1 to avoid the banner message.

Related ABP docs / support answers

• How to register Blazorise license key / ProductToken:
  https://abp.io/support/questions/9891/How-do-I-register-the-Blazorise-license-key
• How to get and use Blazorise license in ABP Projects:
  https://abp.io/support/questions/9912/How-to-get-and-use-Blazorise-License-in-ABP-Projects

Concern / request

I understand the banner is introduced by Blazorise, but the issue for ABP community users is:

• ABP currently pins Blazorise to versions that show the banner (>= 1.8.3)
• downgrading is not possible due to Volo.Abp.BlazoriseUI dependency constraints
• the only "official" solution becomes obtaining and configuring a Blazorise ProductToken, but community users do not have an ABP commercial license / bundled Blazorise PRO access.

Questions

1. Is it intended that ABP community Blazor templates effectively require a Blazorise commercial token to prevent a persistent in-app message in production?
2. Can ABP provide a supported path for community users, such as:
   • allowing Volo.Abp.BlazoriseUI to support a lower Blazorise version range (e.g. 1.8.1) or
   • providing an alternative UI integration package that does not depend on Blazorise (e.g. optional switching) or
   • providing a documented way to replace Blazorise integration in ABP without forked ABP packages?
3. If ABP plans to keep upgrading Blazorise versions (e.g. 10.0.2 mentions upgrading Blazorise packages), what is the recommended long-term strategy for community users?

Thanks.

[omer-repo]

Additional context / precedent (why this matters for ABP community users)

ABP has previously taken action to avoid “forced” commercial dependencies for the community ecosystem. Two relevant examples:

• ABP Issue about IdentityServer/Duende licensing impact:
  Announcement of plan to replace the IdentityServer #11989

• ABP’s move away from AutoMapper (and discussion of alternatives / Mapperly):
  https://abp.io/community/articles/best-free-alternatives-to-automapper-in-.net-why-we-moved-to-mapperly-l9f5ii8s

This is why the current situation with Blazorise feels inconsistent for community/OSS users:
ABP Blazor UI currently hard-depends on Blazorise via Volo.Abp.BlazoriseUI, and ABP pins Blazorise to versions that display the persistent “free version” banner unless a valid ProductToken is provided.

Also, while Blazorise provides a “Free Community License”, their eligibility terms explicitly state:

"Eligibility: Blazorise Community Licensing is reserved for individual developers. Please note, company or organizational use is not permitted."

So for many community ABP users (working in a company/organization), the Blazorise “free” option is not applicable by definition, and the downgrade workaround is blocked by ABP’s package constraints.

[maliming]

hi

Blazorise is free if your yearly income is below a certain amount. For more info, visit its own website.

See #14486

Thanks.

[omer-repo]

Hi,
Thank you for response.
Unfortunately, it is changed in 2023 (https://blazorise.com/news/2023-changes-to-blazorise-plans-and-licensing)

we're implementing new licensing terms starting July 15th, 2023:

The Community license, which will remain free, will be available exclusively for individual users.
All companies must purchase a Commercial license regardless of their size or revenue.

Also, it is not possible to claim a community license now (Megabit/Blazorise#6347)

[maliming]

hi

I will provide feedback to the team.

Thanks.