[Blazor] Prepare for custom cache removal

[maraf]

In the dotnet/runtime#114901 we are removing custom cache. The current auto render mode detection is based on assumption "has user previously used the current version (hash) of application?". Whether custom cache was used or not should not matter, as proper HTTP cache should ensure all the assets are cached.

• Disable custom cache in tests
• Update custom cache related tests to just test subsequent app visit results in 304 for all requests

[maraf]

As discovered in #61790, we need to update tests

[javiercn]

@maraf auto used that to determine when it needed to start in wasm mode vs when it needed to start in server mode. How are we handling that?

[maraf]

Both tests failing on CI passed locally, re-trying

• CanPersistMultiplePrerenderedStateDeclaratively_Auto_PersistsOnWebAssembly
• AutoRenderMode_UsesBlazorServerOnFirstLoad_ThenWebAssemblyOnSuccessiveLoads

[maraf]

@maraf auto used that to determine when it needed to start in wasm mode vs when it needed to start in server mode. How are we handling that?

@javiercn It has it's own local storage item with value of assemblies hash. The check for cacheBootResources eliminated WebAssembly if cacheBootResources was disabled and the client relied on HTTP cache only

[javiercn]

@javiercn It has it's own local storage item with value of assemblies hash. The check for cacheBootResources eliminated WebAssembly if cacheBootResources was disabled and the client relied on HTTP cache only

If I understood this correctly, we are putting a hash on local storage to track this? who's putting the hash (Blazor? the wasm runtime?) Where does it get it from? (since there's no longer a blazor.boot.json file)

[maraf]

https://github.com/dotnet/aspnetcore/blob/main/src/Components/Web.JS/src/Services/WebRootComponentManager.ts#L473-L479

I didn't need to touch this implementation. Blazor already did it this way.
It fetches dotnet.js which now already contains boot config. The hash is present on embedded config. BLazor compares new hash with previous and if matches, it uses WebAssembly.

New updates