-
Notifications
You must be signed in to change notification settings - Fork 311
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
Could not scan /usr/local/share/dotnet/packs/Microsoft.AspNetCore.App.Ref/9.0.0/ref/net9.0/Microsoft.JSInterop.dll for Fable plugins #3974
Comments
Hello, Last time I worked on Fable plugin loading, I was not able to determine why we can't scan some of the assemblies for plugins. In theory, this warning is harmless I kept it because otherwise we had a silent error or the compiler would continue but with an unexpected result. Does the associated Currently Fable scan all the assemblies for plugins, but if we could identity assemblies that we know for sure don't contains Fable plugins we could either not scan them or not report the errors. For example, we know that any .NET Standard assemblies will never contains a Fable plugins. The question is how do we identify them? |
The list of core assemblies is just hardcoded XD But we could do the same strategy as the project cracker to identify system packages... which is just checking if they start with "Microsoft.", "System.", etc. Here: Fable/src/Fable.Transforms/State.fs Lines 32 to 40 in ffc6ee9
|
that's all I have as info. |
@forki I think what Alfonso is saying is that we could decide that we don't scan assemblies starting with "Microsoft.", "System.", etc. because they probably will never have a Fable plugin in them. I don't think anyone outside of Microsoft can releases package starting with these names. |
Description
In .NET Aspire I always get: Could not scan /usr/local/share/dotnet/packs/Microsoft.AspNetCore.App.Ref/9.0.0/ref/net9.0/Microsoft.JSInterop.dll for Fable plugins
Is there anything I can do to work around that?
The text was updated successfully, but these errors were encountered: