[Pre3] Boot config file name change (blazor.boot.json 👉 dotnet.boot.js)

[guardrex]

#35057 (comment)

[maraf]

There is still possibility of merging the config file completely into the dotnet.js (one of the underlaying scripts behind blazor.web(assembly).js

[guardrex]

I see ... so should this be held off until Preview 4?

[guardrex]

I think I'm going to have to give you some links to look at so that we can see how the current guidance that relates to blazor.boot.json needs to change. Since it's unclear what the final framework setup is going to be, perhaps we should wait to discuss it further until the Preview 4 era toward the end of this month.

Alternatively, we could address it thus far for Pre3 and come back to it at Pre4 for further updates. It's up to you. If you want to work on it now for Pre3, I'll provide links to the current blazor.boot.json content.

[maraf]

Give me the links, please. I'm curious why mention it so much in docs. It should be kind of an implementation detail, opaque to the users

[guardrex]

Here are the links to current mentions. Some of these will probably just require a simple rewording to factor out the offending "blazor.boot.json" mention, but other guidance involves interacting with the file (e.g., integrity guidance and script).

I'll number these, which might make it easier for you to respond on each ...

1. https://learn.microsoft.com/en-us/aspnet/core/blazor/webassembly-lazy-load-assemblies?view=aspnetcore-9.0#onnavigateasync-events-and-renamed-assembly-files

2. https://learn.microsoft.com/en-us/aspnet/core/blazor/host-and-deploy/webassembly/github-pages?view=aspnetcore-9.0#deployment-notes

3. https://learn.microsoft.com/en-us/aspnet/core/blazor/host-and-deploy/webassembly/?view=aspnetcore-9.0#change-the-file-name-extension-of-dll-files ... and notes to the reader that it only applies after 8.0 if the Webcil format is disabled.

4. https://learn.microsoft.com/en-us/aspnet/core/blazor/host-and-deploy/webassembly/bundle-caching-and-integrity-check-failures?view=aspnetcore-9.0 ... AND the script is at 👉 https://raw.githubusercontent.com/dotnet/AspNetCore.Docs/refs/heads/main/aspnetcore/blazor/host-and-deploy/webassembly/_samples/integrity.ps1

The following coverage isn't relevant because it's being versioned out at >=10.0 ...

https://learn.microsoft.com/en-us/aspnet/core/blazor/fundamentals/environments?view=aspnetcore-9.0#set-the-client-side-environment-via-header

[guardrex]

@maraf ... This is next, unless you want to circle around to it later. I can write up Javier's declarative state persistence and circle back to this later.

BTW -- Is this for Pre3 or Pre4?

[maraf]

The rename is preview3. I'll decide this week (I hope Wed or Thu) if we want to merge the config file into dotnet.js.
Is that enough for you?

The powershell script makes me sad, because the actual schema of the config should be internal implementation detail. I think if we want to maintain it, we need to move it to aspnetcore or runtime and include it in some test, otherwise it's quite possible it is not accurate.

[guardrex]

I think so. I'll float a PR to address those mentions of blazor.boot.json. I'll ping you on the PR.

WRT the script, one option is to version it out completely for 10.0 and open an issue to consider what should be done with it in the future, if anything (i.e., it might be permanently dropped). Should I proceed with that plan?

[maraf]

WRT the script, one option is to version it out completely for 10.0 and open an issue to consider what should be done with it in the future, if anything (i.e., it might be permanently dropped). Should I proceed with that plan?

Sounds good to me. I expect the script not to do the job completely even in 9.0 :/

[guardrex]

not to do the job completely even in 9.0

Indeed! I'm not sure what to do about it. There are no reports of it failing to work, but that simply could be due to nobody on 🌍 trying to use it with 9.0. 😆