What is going on here? I have a license. I am concerned that if my ABP license expires, then my clients will get this type of message for Blazorise. What is the situation with this vendor? You eliminated AutoMapper because it went commercial. Fair enough. But why are we dealing with commercial nag pop ups for Blazorise? To be honest the generated UI with Blazorise is not good, that is another conversation all together. But why this? And because of this, your licensing terms being a forever license don't apply because if I let my ABP license lapse, I would need to get a Blazorise license to keep the UI working.
Would love a detailed response to this.
Thanks,
Karim
6 Answer(s)
-
0
- That banner is coming from Blazorise, not from ABP itself. Blazorise is a third‑party UI component library and it shows that message when it decides your app is running without a valid Blazorise ProductToken (or when the token can’t be read/validated in the running UI).
- In ABP’s Blazor templates that use Blazorise, you are expected to configure
options.ProductTokenin the Blazorise registration. If you don’t, Blazorise may display a “license expired / free version” footer/banner.
What you should do in an ABP Blazor solution
Generate / obtain the Blazorise Product Token from Blazorise:
- Go to the Blazorise license page and generate the token:
https://blazorise.com/account/user/manage/license
- Go to the Blazorise license page and generate the token:
Configure it in both places when you use a server + WASM (or Blazor WebApp with interactive/WASM) style solution:
YourApp.Blazor→*BlazorModule.cs→ConfigureBlazorise()YourApp.Blazor.Client→*BlazorClientModule.cs→ConfigureBlazorise()
If you only put it into a server-side secrets file, the WASM/client side may not see it and the banner can appear after navigation (server prerender looks OK, then client becomes interactive and the footer/banner appears). ABP support confirmed this exact symptom and fix.
Two working approaches:
- Hardcode the token in the Client module (simplest).
- Or put it into the WASM
wwwroot/appsettings.jsonso the client can load it.
What happens if your ABP license expires?
- This question is fundamentally about licensing terms (ABP + a 3rd-party vendor). I can’t give a definitive legal/contract answer here.
- Technically, however, the behavior you see is controlled by Blazorise licensing checks. If a running app doesn’t have a valid Blazorise ProductToken (for whatever reason), Blazorise may show the banner. So your concern is valid from a technical dependency perspective: Blazorise can enforce its own licensing in the UI runtime.
Sources
- ABP FAQ (ProductToken guidance): https://abp.io/faq#how-to-get-blazorise-license-key
- ABP support (server vs WASM token visibility and the “appears after navigation” symptom/fix): https://abp.io/support/questions/10664
- ABP support (ProductToken steps): https://abp.io/support/questions/9891
- Blazorise token management page: https://blazorise.com/account/user/manage/license
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.
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post) -
0
Hi Karim,
Thanks for the detailed question. Let me address each concern.
1. The banner — your ABP license already covers Blazorise PRO.
You don't need to purchase a separate Blazorise license. Volosoft has an agreement with Megabit (Blazorise's vendor): every active ABP commercial license includes a Blazorise PRO license at no extra cost.
Please follow this walkthrough to claim and configure the Product Token:
https://abp.io/support/questions/9912/How-to-get-and-use-Blazorise-License-in-ABP-Projects
One thing worth flagging for Blazor WebApp solutions: register the token in both
*BlazorModuleand*BlazorClientModule. The WASM client won't read the server'sappsettings.json, so a server-only configuration lets the banner appear once the client takes over from prerender.2. About the licensing question if your ABP subscription lapses.
Let me check with our licensing team on this and get back to you with a clear answer.
3. MudBlazor support in v10.4.2 — an additional UI option.
In v10.4.2 we're adding MudBlazor as an additional supported UI alongside Blazorise. It's not a replacement — both stay supported, and you can pick what fits your project best. MudBlazor is MIT-licensed if that's a factor for you.
10.4.2 isn't released yet but will ship very soon. Here's a community write-up about it:
https://github.com/abpframework/abp/blob/dev/docs/en/Community-Articles/2026-06-09-mudblazor-in-abp-framework/post.md
Thanks
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post) -
0
Hi Karim,
Following up on point 2 from the previous reply.
The Blazorise PRO license issued through the ABP bundling is set with a very long validity period — the Blazorise portal currently shows "23 years from now" as the license end date on our bundled accounts. So even if you choose not to renew ABP later, the bundled Blazorise license stays valid well beyond that, and the banner won't come back simply because your ABP subscription ended.
You can check your own license end date here:
https://blazorise.com/account/user/manage/license
Thanks
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post) -
0Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)


