I agree, but I still believe the two runtimes can co-exist. If the VB6 form
is a part of a ActiveX DLL, one can probably can make it an MDI child with
the appropriate WinAPI calls? Or use the Form's FromHWND constructor to wrap
the VB6 window with a managed Form class instance?
If they have followed proper design, there ain't
much in the vb6 form but some events
and form elements. Those could quickly
be duplicated in .NET and you wind
up proper .net app that you don't
have to deploy to different runtimes.