[blazor][net7] dotnet..js file name is missing version info
See original GitHub issueActual 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
Issue Analytics
- State:
- Created 7 months ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
asp.net mvc - blazor.server.js file not found
I created a new ASP.NET Core 3.0 Web application and selected the Model-View-Controller option. I wanted to add Blazor Server side, so I...
Read more >ASP.NET Core Blazor JavaScript interoperability (JS interop)
This article explains general concepts on how to interact with JavaScript in Blazor apps. A Blazor app can invoke JavaScript (JS) functions ...
Read more >Call JavaScript functions from .NET methods in ASP. ...
This article explains how to invoke JavaScript (JS) functions from .NET. For information on how to call .NET methods from JS, see Call...
Read more >Run .NET from JavaScript
NET into an existing JS app. In the following example, the JS file on disk is main.js , but any JS filename is...
Read more >ASP.NET Core Blazor file downloads
This article explains how to download files in Blazor Server and Blazor WebAssembly apps. Files can be downloaded from the app's own static ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
it’s just bad file name but the app works fine
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.