Blazor, .NET Runtime and .WASM nuget packages #60335
Unanswered
kenasanion
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
I probably need help because I'm actually curious on how Blazor identifies the actual runtime of where it copies the .wasm packages to the publish folder (and I'm not sure if i'm in the right forum). The issue is we're encountering integrity check errors when there is a new runtime being automatically installed in our build server. This causes our integrity check errors in our blazor app since it finds some discrepancies in the checksum between different version of the .wasm coming from the packages.
In our build logs it's like this:
Copying file from "C:\Users\....\.nuget\packages\microsoft.netcore.app.runtime.mono.browser-wasm\**8.0.12**\runtimes\browser-wasm\native\dotnet.native.wasm" to "<project publish folder>"
I want to know how can we force our .NET builds to just use a specific version of the runtime like 8.0.12. Now that 8.0.13 is released, we will encounter the integrity again since it will prefer the nuget packages under 8.0.13. Is it something we can control over our project level or build level? Do we need to explicitly state or force it somewhere?
Btw, we also use global.json in our build but it always uses this latest runtime. I tried different rollFoward options but it always uses the latest runtime patch installed in our build server.
As a workaround, we always clear up our .br and .gz files before build :)
Thanks in advance,
Ken
Beta Was this translation helpful? Give feedback.
All reactions