Update to .NET 10 and use static rendering#4
Merged
Conversation
- Following guide at https://learn.microsoft.com/en-us/aspnet/core/ migration/70-to-80?view=aspnetcore-10.0&tabs=visual-studio#convert-a-blazor-server-app-into-a-blazor-web -app
- Fix bug where refresh would only fire twice
- Use MapStaticAssets
- Fix duplicate HTML tag IDs
bartonjs
approved these changes
Mar 16, 2026
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
2 participants
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.
This upgrades to .NET 10 and updates apireview.net so that its primary functionality of viewing the backlog can be done with pure server-side rendering avoiding unnecessary reconnects. This uses the newer
AddRazorComponentsAPI rather thanMapBlazorHub.Interactivity is still enabled specifically for Publish.razor, but for the rest we rely on static server-side rendering with a little bit of JS for some interactivity. I was able to test most of the pages locally except Publish.razor, but that's what's stayed the most the same.
The schedule/calendar view is rendered on the server using Pacific Time (PT), but JS is used to update the entries to local time if it would still fall on the same day. If it would fall on a different day, the time is labeled with PST or PDT as appropriate.