Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NET9 - warnings on building Blazor Wasm project (WASM0060, WASM0062, WASM0001) #110870

Open
1 task done
konstantin-karpukhin opened this issue Dec 11, 2024 · 4 comments
Open
1 task done
Assignees
Labels
arch-wasm WebAssembly architecture area-System.Runtime.InteropServices.JavaScript os-browser Browser variant of arch-wasm
Milestone

Comments

@konstantin-karpukhin
Copy link

konstantin-karpukhin commented Dec 11, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Describe the bug

1>WasmApp.Common.targets(793,5): Message WASM0060 : Type System.Object is not blittable: Not a ValueType
1>WasmApp.Common.targets(793,5): Message WASM0062 : Type System.Runtime.InteropServices.HandleRef is not blittable: Field _wrapper is not blittable
1>WasmApp.Common.targets(793,5): Warning WASM0001 : Could not get pinvoke, or callbacks for method 'ExternalLibrary.ExternalClass::GetCharABCWidthsFloat' because 'System.NotSupportedException: Unsupported parameter type in method 'ExternalLibrary.ExternalClass.GetCharABCWidthsFloat'
at PInvokeCollector.g__CollectPInvokesForMethod|6_0(MethodInfo method, <>c__DisplayClass6_0&)
at PInvokeCollector.CollectPInvokes(List1 pinvokes, List1 callbacks, HashSet`1 signatures, Type type)'

Expected Behavior

No warnings (as it was in NET8)

Steps To Reproduce

https://github.com/konstantin-karpukhin/BlazorWASM0001

Exceptions (if any)

Project should be configured for NET9 with WasmEnableSIMD set to false

.NET Version

No response

Anything else?

No response

@javiercn javiercn transferred this issue from dotnet/aspnetcore Dec 20, 2024
@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Dec 20, 2024
@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label Dec 20, 2024
@jeffschwMSFT jeffschwMSFT added the arch-wasm WebAssembly architecture label Jan 6, 2025
Copy link
Contributor

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

@vcsjones vcsjones removed the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Jan 6, 2025
@pavelsavara
Copy link
Member

Related ? #112963

@pavelsavara pavelsavara added this to the 10.0.0 milestone Feb 27, 2025
@dotnet-policy-service dotnet-policy-service bot removed the untriaged New issue has not been triaged by the area owner label Feb 27, 2025
@pavelsavara pavelsavara added the os-browser Browser variant of arch-wasm label Feb 27, 2025
@lewing
Copy link
Member

lewing commented Feb 27, 2025

This warning is generated to indicate that the code will fail at runtime (and it will). The logic that is generating the warning could (and should) be improved to understand the SupportedOsPlatform attribute. For now I would suppress the warning.

@lewing
Copy link
Member

lewing commented Feb 27, 2025

Related ? #112963

Weakly related

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
arch-wasm WebAssembly architecture area-System.Runtime.InteropServices.JavaScript os-browser Browser variant of arch-wasm
Projects
None yet
Development

No branches or pull requests

5 participants