We have some Reflection utilities that rely heavily on the MetadataLoadContext
and PathAssemblyResolver
classes (they enable us to analyze the types without incurring in the full cost of loading the full assembly into the execution context).
We have tried using them (client-side) from a Blazor WebAssembly App.
We are having difficulty specifying the paths to the PathAssemblyResolver
class (we know the target DLLs are there, but they don't seem to be accessible via the sandboxed filesystem). Is there a way where we could coax the PathAssemblyResolver
to locate the DLLs?
We know that as a workaround, the analysis could be performed on the server side, but are very interested in learning the possibilities as well as the limitations of Blazor WebAssembly technology.
Aucun commentaire:
Enregistrer un commentaire