-
Notifications
You must be signed in to change notification settings - Fork 25.3k
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
Document how to setup callbacks for native dependencies in Blazor WebAssembly #23661
Comments
You read my mind, Dan. I was just about to open an issue |
This is currently a section of the Blazor WASM host and deploy doc at ... @danroth27 ... I'm 👂 if you prefer a dedicated topic for this content. I could set that up along with the work to resolve this issue. If a dedicated topic, do you want it in the Host and deploy node? |
Native dependencies aren't really a deployment concern; they are a development concern. You need to be able to use your native dependencies during development. So I think this deserves a dedicated topic. |
I'll set it up first thing tomorrow morning with the updates to address this issue. Seems like it will be one of our "floating" Blazor topics out in the open Blazor node. |
Currently the section Blazor WebAssembly: Use (native) libraries which uses SkiaSharp as an example The mentioned SkiaSharp.Views.Blazor has the following dependencies one of the dependencies: SkiaSharp.NativeAssets.WebAssembly packs a static library libskiasharp.a Questions1==> for users who are interested to use other native libraries (e.g. Question2The TorchSharp native assets are huge. Is there size limit of currently implementation of Blazor WebAssembly for using native libraries? |
Hey guys, I came across this problem in which having a C#9 function ptr in the |
@Alan-FGR ... Normally, we don't work on closed issues/PRs, so I would direct you to open a new issue from the bottom of the native deps topic. However, it looks like from your remark that you should file a support request with the product unit instead. Open for them at ... https://github.com/dotnet/aspnetcore/issues Please add ...
... to the bottom of your opening comment so that I can follow along. I might open a new docs issue for the native deps article based on what they say. I'll keep an 👁️ on your issue if you open one over there. |
[EDIT by guardrex to add the metadata]
See dotnet/runtime#60824 (comment).
@lewing @radical @lambdageek
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: