Host the CLR and Generate IL to call a MessageBox

Interesting Finds: August 7, 2006

Jason Haley — Tue, 08 Aug 2006 05:23:45 GMT

Rob Herbst :: Host the CLR in C++

Rob Herbst :: Host the CLR in C++ — Tue, 08 Aug 2006 06:21:40 GMT

PingBack from http://www.robherbst.com/blog/2006/08/07/host-the-clr-in-c/

re: Host the CLR and Generate IL to call a MessageBox

Jochen Kirstätter — Tue, 08 Aug 2006 18:05:27 GMT

Hi Calvin,

nice shot. I experimented some stuff writing a host for CLR inside of Visual FoxPro. I created an FLL to ease usage in VFP. On of my next steps is to create an object reference (added to _VFP or _Screen) in order to execute .NET assemblies in VFP. Second, I'm stuck with configuring my own ApplicationDomain for VFP to separate memory stuff from the default app domain.

Maybe this could be an idea to extend Sedna... ;-)

Anyway, here's the C++ code I use inside my FLL to create the CLR host:

HRESULT hr = CorBindToRuntimeEx(
NULL,
NULL,
0,
CLSID_CLRRuntimeHost,
IID_ICLRRuntimeHost,
(PVOID*)&pRuntimeHost);

This way, always the latest, installed version of .NET Framework is returned. Would be nice to share some thoughts about writing an CLR Host for VFP.

Kind regards, Jochen "JoKi" Kirstätter

re: Host the CLR and Generate IL to call a MessageBox

rstrahl — Wed, 09 Aug 2006 08:36:26 GMT

So how would this be more benficial than say doing COM interop into the CLR which automatically creates a default AppDomain?

I can see this being useful for pure C++ code, but I'm not sure I see the immediate benefit for doing this higher up the stack for say FoxPro or VB 6 since you still need to pass data across somehow. I don't think that there's a big performance gain either when you compare COM interop vs. directly calling into the CLR.

Can you give a use case when this would be useful?

I'm just thinking out loud here. A while back I built an Add-in interface into Help Builder for example, that allows Add-in creation in .NET even though the application is a FoxPro application. It uses COM interop and that works just fine. i just don't see the benefit of a 'pure' .NET hosting situation unless you need to have a primary gateway (ie. IIS, IE etc.).

re: Host the CLR and Generate IL to call a MessageBox

rsl — Tue, 19 Dec 2006 08:50:52 GMT

Hi Calvin,

Thanks for the information. I've tried doing the same way to use my managed c++ code in unmanaged c++ . But the API ExecuteInDefaultAppDomain(..) fails. May I know why is it so?

Regards,

RSL

Good site

Olgunka-ev — Wed, 05 Nov 2008 08:49:59 GMT

<a href= http://index1.ystins.com >laguardia rising stars 2006</a> <a href= http://index2.ystins.com >northumberland county va</a> <a href= http://index3.ystins.com >holy ghost prep bensalem craft</a> <a href= http://index4.ystins.com >miles away from the ordinary</a> <a href= http://index5.ystins.com >star trader software</a>