Fixes #4062: App.razor - moves loading body resources above blazor.web.js

[thabaum]

Pull Request

Fixes #4062

Description

Moves resources loading in the body of App.razor file above loading the blazor.web.js

Screenshots

[thabaum]

@sbwalker I am not sure I just wanted to share this result, but I am not 100% it does not affect something I am not thinking of in Oqtane. I appreciate your time reviewing.

[sbwalker]

@thabaum basically you moved all statically defined JS references to the end of the body section - correct?

[thabaum]

@sbwalker yes, and this improved logging out interactive/auto mode blink of an eye...

[sbwalker]

@thabaum I believe logout performance was improved by #4043 and is not related to this change

[thabaum]

@sbwalker I pretty much main thing is put the blazor.web.js at the end as this pulls off all the magic tricks.

[thabaum]

@sbwalker after further review, not sure how I ended up wtih those results shown, but this PR does not do it. And when I had those results it worked great in interactive auto mode. Anyhow this can be reverted back unless it does not seem to cause any issues.. my apologies. Somehow I had it show me this source, and also the interactive/auto ran fast logging out, now I cannot reproduce this behavior or make the code get displayed as shown. Strange... you can see in #4062 screenshot it is the same editor.

I am not sure what to think here as I am pretty sure I generated those results above somehow while in Interactive/Auto. While I could produce those results seems like it would log out rapidly.

Maybe I am just experiencing some glitches in VS? Or is there something finding scripts in the page body and re-writing them in oqtane?

I am updating visual studio now, it may have bugged me up as I didn't notice it was available.

[sbwalker]

@thabaum I don't think it has an impact on the actual framework at run-time, but I do like the idea of the Blazor JS reference being at the very bottom of the body so I will not revert this PR.