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
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:
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 Original error message contains some meaningful information?
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?
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: