Marc Zwart

@ScarletKuro @henon looking forward to hearing back, I am eager to fix this :) (if you approve)

Hey all, This is a great .net 9 feature and imo should remain enabled. Look into adding .MapStaticAssets to your program.cs and refer to the js file through the ComponentBase.Assets...

Ah good old backward compatibility.. Fair point. I will test how this behaves in my project that targets net9 and report back.

I have noticed in my net9 migration that only project files **present in the wwwroot at the start of the build** are included in the fingerprinting process. It might be...

Regarding backwards compatibility, perhaps we could update the init.razor to something like: ``` @namespace BlazorApplicationInsights @if (!IsWasmStandalone) { @((MarkupString)script) } @code { private string GetScriptSrc() { string src = "_content/BlazorApplicationInsights/BlazorApplicationInsights.lib.module.js";...

@IvanJosipovic It seems like v3.2.1 fixes the issue described by @ysmoradi. However fingerprinting is now being opt-out entirely, meaning even when included in another project (net9+) fingerprinted urls are not...

There appear to be some issues with the fingerprinting feature, I am unsure what is the point of exporting fingerprinted files in a nuget package in the first place, that...