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

Why does frida-clr depend on WPF? #12

Open
daddycocoaman opened this issue Sep 21, 2022 · 2 comments
Open

Why does frida-clr depend on WPF? #12

daddycocoaman opened this issue Sep 21, 2022 · 2 comments

Comments

@daddycocoaman
Copy link

Hi,

I was just wondering why frida-clr depends on WPF libraries to use (namely System.Windows.Threading)? With the advancement of .NET/.NET Core over the years, is this still necessary? The use of Forms seems like more than what's required for normal Frida usage and it makes using things like Script.Post really unintuitive.

@hostar
Copy link

hostar commented Jan 14, 2023

I tried to remove the dependency, so far it seems to work. Feel free to try it
https://github.com/hostar/frida-clr/tree/dispatcher-removed

(You need to somehow incorporate it to your local build manually.)

@ekologic
Copy link

ekologic commented Sep 23, 2023

But still it requires WPF dll (PresentationCore) in Process.hpp, Marshal.hpp, Device.hpp and by quickly looking at the usage, it is mainly required for ImageSource and for icons. I wonder if we can just return Bitmap in order to use in other frameworks, such as Avalonia

Edit:
Yeah the dispatcher is in WPF dll

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

3 participants