Let's assume IsWasmStandalone="false" (the default).
Currently, the configuration is expected to be provided through pre-rendering (the ApplicationInsightsInit component emits the script tag with the configuration included). However, the instructions and samples still direct you to provide the connection string in the .Client project as well. The connection string provided to the client is not used unless you manually call AppInsights.UpdateCfg().
This should be consolidated.
My proposal:
Provide the script with the initial configuration from the server if static server-side rendering/pre-rendering occurs.
Modify the script to prevent multiple loads (see this example for inspiration). This change would allow removing the if (!IsWasmStandalone) check from ApplicationInsightsInit.razor and enable it to always initialize.
In ApplicationInsightsInit.razor.cs:OnAfterRender(), under firstRender call UpdateCfg() with merging logic to preserve the server-rendered connection string, ensuring it's not overwritten on the client side, where a duplicate connection string configuration won't be needed.
Let's assume
IsWasmStandalone="false"(the default).Currently, the configuration is expected to be provided through pre-rendering (the
ApplicationInsightsInitcomponent emits thescripttag with the configuration included). However, the instructions and samples still direct you to provide the connection string in the.Clientproject as well. The connection string provided to the client is not used unless you manually callAppInsights.UpdateCfg().This should be consolidated.
My proposal:
if (!IsWasmStandalone)check fromApplicationInsightsInit.razorand enable it to always initialize.ApplicationInsightsInit.razor.cs:OnAfterRender(), underfirstRendercallUpdateCfg()with merging logic to preserve the server-rendered connection string, ensuring it's not overwritten on the client side, where a duplicate connection string configuration won't be needed.cc @jirikanda