Actually you can use COM/ActiveX in VB.NET - .NET creates Interops to
handle communication between the components.
However, I guess Microsoft is expecting you to move away from COM/ActiveX
because for the most part it's unmanaged.
As more .NET components become available, we may see a drop in the
popularity of COM components. Then again, COM components with within the
..NET framework and outside of the .NET framework... so I doubt COM or
ActiveX will go away anytime soon.
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.
