Blazor WebAssembly lazy loading assemblies not working when using @ref attribute in the component

[ajithr]

Describe the bug

• When using Blazor WebAssembly lazy loading assemblies with component's @ref attribute, the corresponding assembly could not load issue throws in the browser console and the application not running.

To Reproduce

https://github.com/ajithr/blazor-wasm-lazy-ref

• Check out the above repo and open ~/LazyLoadingRef/LazyLoadingRef.csproj file in the VS 2019.
• Run the application it will throw exceptions in the browser console.
• Open ~/LazyLoadingRef/Pages/Counter.razor file and remove @ref attribute and LazyLoadComponent reference in the @code section.
• Run the sample again and it will work properly with the lazy loading feature.
  

Exceptions (if any)

Further technical details

• ASP.NET Core version - .net5.0

• Include the output of dotnet --info
  

• The IDE (VS / VS Code/ VS4Mac) you're running on, and its version
  

[javiercn]

@ajithr thanks for contacting us.

This seems to be an issue, I can't tell there's anything wrong from looking at the code.

@captainsafia do you have any thoughts?

Thank you for contacting us. Due to a lack of activity on this discussion issue we're closing it in an effort to keep our backlog clean. If you believe there is a concern related to the ASP.NET Core framework, which hasn't been addressed yet, please file a new issue.

This issue will be locked after 30 more days of inactivity. If you still wish to discuss this subject after then, please create a new issue!

[ajithr]

@mkArtakMSFT @javiercn @captainsafia The issue is closed itself by msftbot. Do we really need to create a new issue report for this? It is not yet discussed and it is under investigation.

[captainsafia]

@ajithr Thanks for the following up. Reopening this issue and moving to backlog.

I had a hunch that this might be caused by some issues that existed in the codepaths used for assembly loading in the WASM runtime. We'll need to (1) validate if this still happens in .NET 6 and (2) investigate why if it does.

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.