Hi,
I have a classic Win32 application, which should stay developed for some
more time, until a brand new product is finished. It would be nice to write
new modules in .NET WinForms and dock them as child windows in the old Win32
Frame window. Is this thinkable ?

The issues I see:
1. Child window relationship
I can use SetParent API to host the child Form, this looks to work fine. But
when the form gets hidden and shown again, it gets new window handle. Is
this behavior described anywhere ?

2. Message loop
Can the hosting Win32 application do message handling also for .NET windows
just with GetMessage/TranslateMessage/DispatchMessage? It appears to work
but I have strange feeling about going around .NET's message loop ... Using
separate threads would be better, I think, but much less comfortable.

Is there a clean way to do this or is it impossible ? I will appreciate all
opinions and resources.

I remember there was a possibility to register a .NET control as ActiveX in
Beta version of Framework. How did that work ? Could it be used anyhow now ?

Thanks for answers,
Jan