Add .net10 support, remove dead code, rework how dlls are retrieved#190
Merged
ScarletKuro merged 11 commits intomainfrom Feb 24, 2026
Merged
Add .net10 support, remove dead code, rework how dlls are retrieved#190ScarletKuro merged 11 commits intomainfrom
ScarletKuro merged 11 commits intomainfrom
Conversation
|
Contributor
|
Looks good, verified on Chrome, Edge, Firefox, both incognito and regular. Only odd thing is what we discussed very first time I ran the project it just "stood" there for multiple minutes after I hit Play. Might have been some initial download I needed? Thank you! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



.NET 10 broke the
dotnet-resources-/cache that we relied on to fetch reference assemblies for Roslyn compilation. There is no longer a blazor.boot.json, the boot config is now inlined insidedotnet.jshttps://learn.microsoft.com/en-us/aspnet/core/blazor/host-and-deploy/webassembly/bundle-caching-and-integrity-check-failures?view=aspnetcore-10.0First I tried this approach (commit bb64f77): fetched
_framework/dotnet.jsat startup, parsed its embedded JSON to resolve fingerprinted assembly filenames (e.g. MudBlazor.abc123.dll), then fetched each DLL over HTTP to build RoslynMetadataReferenceobjects. Complex and slow.New approach: uses
Assembly.TryGetRawMetadata()to read PE bytes directly from assemblies already loaded in the WASM process, zero HTTP requests.Dead code removed:
getCompilationDlls,putInCacheStorage,clearCache,convertBase64StringToBytes,convertBytesToBase64String,CACHE_NAME, etc all gone.