-
Notifications
You must be signed in to change notification settings - Fork 198
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
[NativeAOT-LLVM] DotnetJS JSExport fails, when function was defined in a Browser class library #2626
Comments
Looks like NativeAOT-LLVM implementation relies on source gen to output Is it planned to sync this part with upstream? Or maybe add reflection fallback in NativeAOT-LLVM solution. Otherwise, it doesn't seem possible to reuse class libraries with interop between two browser runtimes. |
Actually, the problem is a bit deeper that I thought at first. |
Might be related #2045 |
The native compiler works by selecting a set of "root" entities as the starting point: the entry point, and UCO methods with an <ItemGroup>
<UnmanagedEntryPointsAssembly Include="YourClassLibraryAssemblyName" />
</ItemGroup> Either in the application, or, for NuGets, in the package Ideally, this would of course be unnecessary, but it is not clear to me yet what the solution would look like. |
Repro:
getAssemblyExports
to execute exported method from JS.Error message
Repro project:
ClassLibrary-2.zip
^ Note, ClassLibrary doesn't use the same runtime nugets, and is compiled with standard JSExport source generator.
The text was updated successfully, but these errors were encountered: