Activities of "maliming"

hi

I’ll fix it as soon as possible and share a temporary solution. Your current ticket has been refunded.

Thanks.

Hi,

This error happens because the new App.razor model uses SSR prerendering by default. During prerendering, JavaScript interop is not available — it can only be called in OnAfterRenderAsync.

In your old _Host.cshtml setup with render-mode="Server", there was no prerendering, so JS interop calls in OnInitializedAsync worked fine. After migrating, those same calls will fail during the prerendering phase.

To help you fix this, could you share the following files:

1. App.razor
2. Your Blazor module class (e.g., MyProjectNameBlazorModule.cs)
3. The full stack trace of the exception
4. Are you using any third-party Blazor component libraries?

Thanks

: )

: )

Hi,

Yes, these optimizations will be included in the next ABP release (10.3). Once you upgrade to 10.3, you can remove all 4 files we provided.

For now, please keep the patch files as they are — they're working well and giving you better performance than the framework changes alone (especially the bulk cache optimization for Redis).

Thanks

The enhanced PR: https://github.com/abpframework/abp/pull/25231

Hi,

You can just create a new project with your current CLI version:

abp new BookStore -t app -u blazor-server

The App.razor structure is the same across versions — you can use the new project as a reference to migrate your existing project from _Host.cshtml to App.razor.

Thanks

Hi,

The App.razor in the ABP template is already clean — <AbpStyles> and <AbpScripts> just reference a bundle name, and the actual CSS/JS files are managed through BundleContributor in your modules. You don't need to move anything out of App.razor.

I'd suggest creating a new ABP 9.1.3 Blazor Server project with the same configuration as yours:

Then compare the new project's App.razor and module configuration with your current project. The new template is the best reference for best practices.

Thanks

Hi,

Just to let you know, we've identified several performance bottlenecks in the framework when dealing with a large number of permissions. We'll be making enhancements in a future version to improve this out of the box.

In the meantime, the workaround files we provided should keep things running smoothly for you.

Thanks

Hi,

What issues are you currently running into? Happy to help here.

If there's any sensitive information you'd prefer not to share publicly, feel free to email me at liming.ma@volosoft.com.

Thanks