Hi,

Thank you for reaching out to us.

In our HTML version, we are initializing all of the js code inside the page load event, the page gets refreshed every time you change a route, and this triggers an initialization for each page separately.

Since Blazor Webassembly is a single-page app (SPA) it renders content differently and the page doesn't get reloaded every time you change a route. For SPA you need to handle initialization differently.

Instead of initializing the js code inside the page load event, you can trigger initialization functions in Blazor lifecycle events.

Here is an example:

@inject IJSRuntime JS

@code {
protected override void OnAfterRender(bool firstRender){
JS.InvokeVoidAsync("KTComponents.init");
}
}

protected override async Task OnAfterRenderAsync(bool firstRender)
 {
 // await asynchronous request here
 await ...
 // reinitialize components
JS.InvokeVoidAsync("KTComponents.init");
 }

Thanks Lauris, it helps.

Then, taking as example the Subscriptions List page https://preview.keenthemes.com/metronic8/demo30/apps/subscriptions/list.html, is it correct to assume that all the assets included in the sections identified by the comment `(mandatory for all pages)` can be added in the index.html page, and those included in the section `used for this page only` must be imported in the OnAfterRender override?
And then call the init for every js file imported, looking at the KTUtil.onDOMContentLoaded function included in any of them.
Does it make sense?

Thanks.

Hello.

Can you share how you managed to add Metronic theme in Blazor WASM? There is no step by step guide on how to achieve that and as it looks like we won't get Blazor WASM StarterKit anytime soon.

Thanks!