🚀 go-pugleaf

"Bob Piskac" <bob@pbsoftware.com> wrote in message
news:45319f54$1@newsgroups.borland.com...

> I wrote a simple C++ application to call a .NET c# assembly that ruturned
> a c# string.  Is it possible to have a .NET control work on my win32
window?

In what way exactly?  Please be more specific.

Have you read the MSDN documentation yet about hosting the .NET runtime in
your application?

    Hosting the Common Language Runtime

http://msdn.microsoft.com/library/en-us/cpguide/html/cpconhostingcommonlanguageruntime.asp


Gambit

Remy Lebeau (TeamB) wrote:
> 
> In what way exactly?  Please be more specific.
> 

Simple example. I want to display a managed code button in my unmanaged 
CPP application.


> Have you read the MSDN documentation yet about hosting the .NET runtime in
> your application?
> 
>     Hosting the Common Language Runtime
> 
> http://msdn.microsoft.com/library/en-us/cpguide/html/cpconhostingcommonlanguageruntime.asp
> 
> 
> Gambit
> 
> 

No, I will read it.

"Bob Piskac" <bob@pbsoftware.com> wrote in message
news:453e737f$1@newsgroups.borland.com...

> I want to display a managed code button in my unmanaged CPP application.

Managed controls can only (officially) appear inside of other managed
controls and managed windows.  There is no direct access available to
specify an unmanaged owner window for a managed control.  So you will need
to either have your unmanaged application tell the assembly to show its own
managed window, or else you will have to use PInvoke to call the Win32 API
SetParent() function to reparent the managed control's Handle to an
unmanaged parent window.


Gambit

Let me see if I understand correctly....

1) From my unmanaged CPP application I call PInvoke and pass my window 
handle.
2) In my .NET class function I get the handle as a parameter and call 
the win32 API SetParent().

It's that easy?

Remy Lebeau (TeamB) wrote:
> "Bob Piskac" <bob@pbsoftware.com> wrote in message
> news:453e737f$1@newsgroups.borland.com...
> 
>> I want to display a managed code button in my unmanaged CPP application.
> 
> Managed controls can only (officially) appear inside of other managed
> controls and managed windows.  There is no direct access available to
> specify an unmanaged owner window for a managed control.  So you will need
> to either have your unmanaged application tell the assembly to show its own
> managed window, or else you will have to use PInvoke to call the Win32 API
> SetParent() function to reparent the managed control's Handle to an
> unmanaged parent window.
> 
> 
> Gambit
> 
> 

"Bob Piskac" <bob@pbsoftware.com> wrote in message
news:453f5c29$1@newsgroups.borland.com...

> From my unmanaged CPP application I call PInvoke and pass
> my window handle.

PInvoke is a .NET function for calling unmanaged APIs.  The .NET code will
have to use PInvoke in order to call SetParent() from the managed
environment.  Your unmanaged environment has direct access to SetParent().
Your .NET code will have to export its own function that the unmanaged code
can call.  Unless you have access to the .NET Control object in your
unmanaged code, in which case the unmanaged code can access the
Control.Handle property and then make the call to SetParent().


Gambit