You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using lazy loading in a Blazor WebAssembly app you have to specify which assemblies you want to lazy load using the BlazorWebAssemblyLazyLoad item group. Prior to .NET 8 you would specify the assembly name with the .dll file name extension. In .NET 8 we introduced webcil packaging, which caused an unannounced breaking change in lazy loading to require you to specify the .wasm extension instead, which has impacted users trying to upgrade.
We should consider fixing this breaking change by continuing to support the earlier .dll file names in addition to the .wasm file names and have the framework handle mapping the .dll file names appropriately.
The text was updated successfully, but these errors were encountered:
When using lazy loading in a Blazor WebAssembly app you have to specify which assemblies you want to lazy load using the
BlazorWebAssemblyLazyLoad
item group. Prior to .NET 8 you would specify the assembly name with the .dll file name extension. In .NET 8 we introduced webcil packaging, which caused an unannounced breaking change in lazy loading to require you to specify the .wasm extension instead, which has impacted users trying to upgrade.We should consider fixing this breaking change by continuing to support the earlier .dll file names in addition to the .wasm file names and have the framework handle mapping the .dll file names appropriately.
The text was updated successfully, but these errors were encountered: