Inject .net application into native Process

[Jadd]

How are you shadow loading them in the main app domain? I searched and it looks like you cannot set up the main app domain to shadow load assemblies.

You *could* manually map the PE (or shadow-copy it yourself to a temp directory like the CLR does) to avoid file locks; you'll also need to modify the display name every time it is loaded, to avoid having the binder caching your assembly. You'll be able to inject/run your assembly, then modify your assembly, then inject and load it again. But the previous ones will still exist in the same app domain. If you're that fussy, just use a native CLR host bootstrap.

But I use a bootstrap assembly specifically to avoid ever having to recompile it (Bootstrap.cs * GitHub). It's easier.

[MaiN]

But I use a bootstrap assembly specifically to avoid ever having to recompile it (Bootstrap.cs * GitHub). It's easier.

Yes, that is my point. This is the method I have used for years now, ever since Apoc posted his first loader. But lolp1 said that it works for him without the separate non-changing loader, which is what I'm curious about. He's saying that there is no need to use any separate DLL loader handling the app domains.

[lolp1]

Yes, that is my point. This is the method I have used for years now, ever since Apoc posted his first loader. But lolp1 said that it works for him without the separate non-changing loader, which is what I'm curious about. He's saying that there is no need to use any separate DLL loader handling the app domains.

Sorry for the late reply. I currently use the domain wrapper answer due to the complexity using the other answer causes when using obfuscation.. if I recall you may need to change this:

_domain = AppDomain.CreateDomain("Gather.NET.Internal", null, currentPath, null, true);

to something like

int randomInt = new Random(0).Next(100,500);
_domain = AppDomain.CreateDomain($"Gather.NET.Internal{_}{randomInt}", null, currentPath, null, true);

If that does not work let me know and I will go find my example some where on old git backup, since I am 99.99% sure this works as is when I tested the other day. Missed your reply.

[Jadd]

Sorry for the late reply. I currently use the domain wrapper answer due to the complexity using the other answer causes when using obfuscation.. if I recall you may need to change this:

_domain = AppDomain.CreateDomain("Gather.NET.Internal", null, currentPath, null, true);

to something like

int randomInt = new Random(0).Next(100,500);
_domain = AppDomain.CreateDomain($"Gather.NET.Internal{_}{randomInt}", null, currentPath, null, true);

If that does not work let me know and I will go find my example some where on old git backup, since I am 99.99% sure this works as is when I tested the other day. Missed your reply.

You're still missing the point, the explanation you gave earlier makes it seem like you're able to modify the first assembly (the bootstrap,) which I'm pretty confident that you can't. Unless you're taking some additional steps that you didn't elaborate on.

[lolp1]

You're still missing the point, the explanation you gave earlier makes it seem like you're able to modify the first assembly (the bootstrap,) which I'm pretty confident that you can't. Unless you're taking some additional steps that you didn't elaborate on.

You are correct. I had mistaken, while you can reinject and reload loaded assemblies and such that you recompile.. you cant seem to recompile the main project this way. I am going to look into my old code and see if I can figure out what work around I had before -- I am sure at one point I had a class some what like this working we will see though and I will report back