AFAIK it (the workaround you mentioned) is supported for IE and MFC
containers:
http://msdn.microsoft.com/msdnmag/is.../WindowsForms/
Quote:
"While neither Visual Basic 6.0 nor ATL is officially supported in version
1.1 either, the Windows Forms team did a full test cycle on hosting Windows
Forms controls as COM controls in MFC 7.1-the version of MFC that comes with
Visual Studio .NET 2003-and it is now an officially supported unmanaged
host."
I guess manually implementing the COM interfaces neccessary for an ActiveX
control is possible, too; But that's probably more work than porting the
client to .net.
Niki
"Nicholas Paldino [.NET/C# MVP]" <mv*@spam.guard.caspershouse.com> wrote in
news:uu*************@TK2MSFTNGP10.phx.gbl...
Sammut,
No, it is not. Controls in .NET can not be exported as ActiveX
controls. Chris Sells has a workaround, but it is extremely unsupported.
You can find it here:
http://www.ondotnet.com/pub/a/dotnet...mshosting.html
Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com
"Sammut" <sa*****@hotmail.com> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...