Hello,
I recommend the following article from the August issue of MSDN:
http://msdn.microsoft.com/msdnmag/is...op/Interop.asp
detailing how COM clients/servers will be able to interact with
.NET classes/applications.
From what I understand, a COM client application will be able to
call a .NET class as if it was a COM component. Also a form
capable of hosting ActiveX controls (OCXs) will also be able to
host .NET Controls at no additional cost.
Symetrically, a .NET application will be able to call COM components
as if they were native .NET classes, and .NET forms will be able
to host OCXs.
Making PB capable of creating COM components and OCXs would suffice
to make it and excellent addon for the .NET platform, thanks to its
inner qualities (size and speed).
Making PB able to access COM components would give its developers
an instant access to key existing (COM components) and future (.NET
classes) software resources.
Philippe Monteil
JAZZAge Software
------------------
I recommend the following article from the August issue of MSDN:
http://msdn.microsoft.com/msdnmag/is...op/Interop.asp
detailing how COM clients/servers will be able to interact with
.NET classes/applications.
From what I understand, a COM client application will be able to
call a .NET class as if it was a COM component. Also a form
capable of hosting ActiveX controls (OCXs) will also be able to
host .NET Controls at no additional cost.
Symetrically, a .NET application will be able to call COM components
as if they were native .NET classes, and .NET forms will be able
to host OCXs.
Making PB capable of creating COM components and OCXs would suffice
to make it and excellent addon for the .NET platform, thanks to its
inner qualities (size and speed).
Making PB able to access COM components would give its developers
an instant access to key existing (COM components) and future (.NET
classes) software resources.
Philippe Monteil
JAZZAge Software
------------------
Comment