-
-
Notifications
You must be signed in to change notification settings - Fork 117
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
Support for .NET Core #66
Comments
Also, being able to install via |
Hi Not sure if everything is working as before because net core has no AppDomain anymore and the reflection part is different too. Please provide feedback how it works!! |
@zplan this won't work, the only way this will work is to build AsmSpy in two variants, are core variant and a framework variant. AsmSpy doesn't do any of the assembly loading, that is done by the runtime. Framework variant will load from the GAC and the core variant will load from shared assembly folders, but not both. As far as I know the only way to achieve both is to implement your own assembly resolver (like in ILSpy), but the GAC is complex and impossible to imitate. |
My understanding is that. NET 6.0 needs to change DependencyAnalyzer.ResolveFileReferences to use the TypeLoader. Is that correct? |
AsmSpy does not yield useful results when run in a binaries folder of a .NET Core deployment. Is this use case on your backlog? Ideally it will incorporate the runtime's shared assemblies and exclude assemblies in the GAC.
The text was updated successfully, but these errors were encountered: