You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following the advice to enable WasmAllowUndefinedSymbols does allow the build to complete in Debug mode, but attempting to compile in Release instead causes the following error:
Summary of your issue
When migrating from .NET 8 to .NET 9 in Blazor WebAssembly, the WASM runtime package for
OpenCvSharp4
causes compile issues.Environment
Blazor WebAssembly
What did you do when you faced the problem?
I was upgrading a project that uses OpenCvSharp to .NET 9 and encountered this issue. I have provided a minimal reproduction repository here: Riccorbypro/ReproRepo.OpenCvSharp.Blazor.Net9.Compile
Example code:
Note: No actual usage of the library is required, simply including the runtime package is enough to cause the error.
Output:
When publishing, the wasm compiler produces the following:
Following the advice to enable
WasmAllowUndefinedSymbols
does allow the build to complete inDebug
mode, but attempting to compile inRelease
instead causes the following error:What did you intend to be?
The project should compile and publish successfully under .NET9, as is currently the case in .NET8.
The text was updated successfully, but these errors were encountered: