Global Assembly Cache in Browser for Blazor WASM #60644
Unanswered
jatinshah404
asked this question in
Ideas
Replies: 1 comment 3 replies
-
Framework dlls are trimmed to what the actual application is using. Downloading them is one part, but them into the wasm memory is second. Having to load more assemblies / bigger assemblies would increase that part. That's one of the reasons why even general CDN isn't a good option for .NET in the browser. .NET nowadays ships different, you have STS and LTS (and possibly previews) and servicing releases for each. That would mean a browser installer would be probably hundreds of mega bytes. Should browser vendors force that on any user that possibly may never visit a blazor based site? Should they do that for other frameworks as well? |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
When we user try opening a Blazor app in browser , system downloads all .NET framework related DLLs first time. Can we have GAC like feature in browser? where all .NET framework related dlls are already stored and Blazor app can use them without downloading dlls? Is that possible using Edge browser? That way initial load time of Blazor client app will significantly reduced.
Beta Was this translation helpful? Give feedback.
All reactions