[Problem]Start CLRHost in a Bootstrap

[bouh2]

Hi,

I try to inject a managed dll into a process but it never works.

First i tried http://www.mmowned.com/forums/wow-me...Inject+Managed from Shynd, but lpCLRHost->Start() return me an error code (-2147467259)

Then I tried EasyHook, but when i run Config.Register it say that the dll hasn't a strong name (even if I add one)
I have the same message with BabBot


So I need help :/
Has someone a project work ?


Thank's

[MaiN]

Hi,

I try to inject a managed dll into a process but it never works.

First i tried http://www.mmowned.com/forums/wow-me...Inject+Managed from Shynd, but lpCLRHost->Start() return me an error code (-2147467259)

Then I tried EasyHook, but when i run Config.Register it say that the dll hasn't a strong name (even if I add one)
I have the same message with BabBot


So I need help :/
Has someone a project work ?


Thank's

Are you sure you're doing it like this:
Inject bootstrap into target process -> bootstrap starts CLR in target process -> bootstrap executes managed code in target process

Also, be sure to read this on the topic.

Taken from above article:

[bouh2]

I have readed, and readed again this topic.
I inject my bootstrap in the target process (I'm sure, i can debug it) and it bug on starting of CLR.

EDIT : Here is my code

#include <windows.h>
#include "MSCorEE.h"
#pragma comment(lib, "mscoree")


DWORD WINAPI StartTheDotNetRuntime( LPVOID lpParameter);

DWORD WINAPI StartTheDotNetRuntime( LPVOID lpParameter)
{
    ICLRRuntimeHost *pClrHost = NULL;
    HRESULT hr = CorBindToRuntimeEx(
        NULL, L"wks", 0, CLSID_CLRRuntimeHost,
        IID_ICLRRuntimeHost, (PVOID*)&pClrHost);

    hr = pClrHost->Start();

    DWORD dwRet = 0;
    hr = pClrHost->ExecuteInDefaultAppDomain(
        L".\\NetDll.dll",
        L"MyNamespace.MyClass", L"MyMethod", L"MyParameter", &dwRet);

    hr = pClrHost->Stop();

    pClrHost->Release();

    return FALSE;
}


INT APIENTRY DllMain( HWND hDLL, DWORD fdwReason, LPVOID lpvReserved )
{
    switch ( fdwReason )
    {
    case DLL_PROCESS_ATTACH:
        DWORD dwThreadId;
        HANDLE hThread = CreateThread(0, 0, StartTheDotNetRuntime, NULL, 0, &dwThreadId);
        
        break;
    }

    return TRUE;
}

And my managed dll :

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Windows.Forms;

namespace MyNamespace
{
    public class MyClass
    {
        // This method will be called by native code inside the target process...
        public static int MyMethod(String pwzArgument)
        {
            MessageBox.Show("Hello World");
            return 0;
        }

    }
}

Now it's bug on ExecuteInDefaultAppDomain

[LegacyAX]

Just a hint but I think your looking to deeply into "how" instead of "why", the answer seems to be right under your nose and is in your reach. Good luck on your project mate. let us know if you still cant fix it,

also just curious what operating system are you using?

[bouh2]

I see what you say.

I'm under XP SP3 with .Net framework 3.5

EDIT : Ok you had right, its work now
+rep for you

[opulent]

I'm sorry to use an old thread but this is very similar to how I'm calling my managed library and I'm having some issues trying to debug.

I can't seem to find the way to step into the managed .dll within VS2008 to hit breakpoints after ExecuteInDefaultAppDomain() is called.

My managed class library sets up hooks just fine and I can verify that they are indeed getting hit by logging each function call to a text file.

I'm so sorry for posting here, I've been stuck on this for two weeks now... Any ideas?

[lanman92]

I'm pretty sure you can attach onto WoW(or whatever you're injecting into) and breakpoint on your function.

[amadmonk]

I use VS2k8 in this configuration (injected native, injected managed, debugging) all the time. You do have to manually attach after injection, of course, but that shouldn't be blocking you.

What's the specific error?

[opulent]

- The bootstrap and the managed module are in the same solution.
- In VS2008, I attach my solution to wow before injecting it and on injection breakpoints in the native bootstrap are hit enabling me to step through and follow execution. (No biggy)
- The bootstrap uses ExecuteInDefaultAppDomain() to call a function in the managed library which installs an endscene hook.
- The native dll finishes up, The managed hook is installed and getting hit each frame (verified by writing to a text file each hit) but I can't figure out how to attach it in VS2008 to step in and get a breakpoint.

[amadmonk]

Interesting. My setup is almost identical except that the native is C++/CLI (so, mixed native and CLR) and stays resident. I don't do anything else differently.

For me, all the breakpoints are hit. Not entirely sure what the magic is.

[opulent]

Well, Thanks for the replies. At least now I know it works for you, I know that it's possible and I must just be doing something stupid..

[amadmonk]

Actually, mixed-mode debugging (debugging mixed native/managed code) is a bit of a black art, and doing it on an injected binary even more so. So in some ways, I'm more surprised when it works than when it fails. I was working on the visual studio team when they were first implementing that, and a lot of developers lost a lot of sleep trying to make it happen.

Of course, that's no help to you...

[tanis2000]

I've been having your same problem opulent. I have a C# launcher that injects the C bootstrapper that in turn injects the C# dll and here's the line that I added to the injected C# dll in order to make it popup an exception and let me choose a debugger to use:

#if DEBUG
            // We break inside the start of the main thread in order to debug
            System.Diagnostics.Debug.Assert(true == false);
#endif

[Cypher]

I've been having your same problem opulent. I have a C# launcher that injects the C bootstrapper that in turn injects the C# dll and here's the line that I added to the injected C# dll in order to make it popup an exception and let me choose a debugger to use:

#if DEBUG
            // We break inside the start of the main thread in order to debug
            System.Diagnostics.Debug.Assert(true == false);
#endif

I'm no C# expert, but uhh, couldn't you just do:
Assert(false)

?

[adaephon]

Suddenly seems strangely reminiscent of another thread...

On topic, you could try having a separate instance of VS2k8 attached to the WoW exe once your main program has injected your runtime. I can't remember but I believe I had some success with this - didn't get too far with my endeavours in that area as I got too busy with uni / work.

Out of curiosity, have you put specific breakpoints in your injected managed code to see if they are hit? Or are you trying to attach and add breakpoints once attached?