[blazor][net7] dotnet..js file name is missing version info

[pavelsavara]

Actual behavior

The file name of dotnet..8wdpaewqyh.js generated by blazor app is missing version info.

Expected behavior

dotnet.7.0.3.pe05f8nz0f.js

To Reproduce

• SDK 7.0.103
• install wasm-tools 7.0.3
• create simpla blazor wasm app from template
• add <WasmBuildNative>true</WasmBuildNative> to client project file
• dotnet run -bl -c Release

Notes

DotNetJsVersion is used to build the name in _ResolveBlazorWasmOutputs, but it is set much later in the ProcessPublishFilesForBlazor

[pavelsavara]

cc @lewing @maraf @TanayParikh @javiercn

[javiercn]

@pavelsavara is this a "build" only thing? Does the published version get the right version in it?

[mkArtakMSFT]

Ping @pavelsavara
We're trying to understand if something is broken and has to be addressed in a patch in .NET 7 or not.

[pavelsavara]

It doesn't reproduce for you ?

[pavelsavara]

I tested again with 7.0.400-preview.23224.17 and wasm-tools 7.0.5/7.0.100 (SDK 7.0.400-preview.23224).

dotnet run -c Release will indeed produce wrong file name dotnet..o2qge3ran4.js.

It works well with publish

[lewing]

is this with an 8.0.1xx sdk?

[pavelsavara]

no, this is Net7, I have not tried net8

[javiercn]

@pavelsavara is the app functional and the js file contains the wrong name or is it functional?

[pavelsavara]

it's just bad file name but the app works fine

[maraf]

It is caused by native relink on build, not publish.
The SDK bits have moved to Wasm SDK, we will fix it there and backport to .NET 7 SDK here.