[Blazor] AddInteractiveWebAssemblyComponents() should register LazyAssemblyLoader or a similar type.

[javiercn]

• Otherwise, lazy assembly loading breaks during prerendering.
• The workaround/fix is to register the service yourself.
  • builder.Services.AddScoped();

This never worked in the past with webassembly, but it was not as prevalent as we were not doing prerendering.

We can start by registering a mock implementation inside AddInteractiveWebAssemblyComponents, adding a reference is not suitable in a patch release.

[javiercn]

We should consider fixing this issue and #26601 at the same time.

[javiercn]

I don't think we can patch this. It will require us to add a reference to Components.WebAssembly which is changing public API, so I think the best we can do is tell people to register the type themselves.

[mkArtakMSFT]

I don't think we can patch this. It will require us to add a reference to Components.WebAssembly which is changing public API, so I think the best we can do is tell people to register the type themselves.

Sounds like we need to document this as a known issue then?

Thanks for contacting us.

We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.