I have a solution that has many different RCL projects (Main solution is.Net 8 Blazor using InteractiveServer) Each one of the RCL’s has pages in it. I define a page as a component with @page "/someurl"

Used the local SQL connection string for development, starting testing and added KeyVault storage for the connection string in Azure…
So in the project appsettings.json contains the connection string to Azure:

My Blazor server app runs fine on Azure with one server. When I scale it out to two servers, I sometimes get the following. I have session affinity turned off. This clearly is the Blazor framework having problems. Any idea why?

My Blazor server app runs fine on Azure with one server. When I scale it out to two servers I sometimes get the following. I have session affinity turned off. This clearly is the blazor framework having problems. Any idea why?

I have a deployed server-side Blazor application in production that has served many Droid Chrome clients for the past few years. Everything appears to work fine, and I have my own Droid phone that I regularly test with to verify that it works.

I have a Blazor Interactive Server app. On several of my pages I have a component where the user can register for an event. There are 4 buttons (No, Undecided, Interested, Attending). When they click the button, that fires an event that reads 2 records from the DB, updates them with the signup status, and saves them.

Does Blazor Server offer any inbuilt ways of preventing old JavaScript files from being served by browser caches?

Coming from an MVC background, I cannot understand the purpose of Layout.cshtml in a Blazor app. There is also a MainLayout.razor. I know one is a view (cshtml) and another is a component (.razor). But if razor components can’t be used within views, I don’t understand the point of the Layout.