Skip to content
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

Open
cveld opened this issue Feb 3, 2020 · 4 comments
Open

Support for .NET Core #66

cveld opened this issue Feb 3, 2020 · 4 comments

Comments

@cveld
Copy link

cveld commented Feb 3, 2020

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.

@bjorg
Copy link

bjorg commented Apr 17, 2020

Also, being able to install via dotnet tool install would be nice, but .NET Core support first please! :)

@zplan
Copy link

zplan commented May 28, 2021

Hi
I created a fork branch with an update to net5.0
https://github.com/zplan/AsmSpy/tree/feature/UpdateTonet50

Not sure if everything is working as before because net core has no AppDomain anymore and the reflection part is different too.
No installers migrated yet and no binaries, please compile by yourself.

Please provide feedback how it works!!

@Droppers
Copy link

Droppers commented Aug 6, 2021

@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.

@4eyecoder
Copy link

My understanding is that. NET 6.0 needs to change DependencyAnalyzer.ResolveFileReferences to use the TypeLoader. Is that correct?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants