Answered by:
COM INTEROP and .Net Framework

Question
-
Hello,
Does anyone have any idea when when the .Net Framework applications will replace COM interop? I'm converting my vb6 to vb 2008 and I'm finding it easier to use the COM Interop references instead of the .NET ones. But the Intro to COM Interop states, in part:
.NET Framework applications will eventually replace those developed with COM. Until then, you may have to use or create COM objects by using Visual Studio. Interoperability with COM, or COM interop, enables you to use existing COM objects while transitioning to the .NET Framework at your own pace.
Do you know when the .Net Framework applications will replace COM interop?
Are references such as Interop.AutPSTypeLibrary currently the recommended way to interface with PCOM, or has Microsoft already introduced a .Net Framework application to replace the COM interop?
Thank you for any advice you can give me.
Wednesday, August 11, 2010 9:03 PM
Answers
-
I think what they mean is that COM libraries will be replaced by .NET Framework equivalents over time. It's not going to happen all at once. There is no light switch. Once again, this will depend upon Microsoft and third-party vendors to develop .NET replacement libraries and in some cases it probably will never happen.
There have been no plans or announcements that I am aware of to drop COM interop support from Visual Studio and I would sincerely doubt, since it's still rather prevalent, that it would be dropped anytime in the near future. I would expect that there will be less emphasis on COM interop as apps move to the 64-bit world and legacy 32-bit COM heads towards obsolescence, but I think 32-bit apps will be around for a while yet.With respect to PCOM, IBM would be your best source for support. I don't know what their plans are for .NET.
Paul ~~~~ Microsoft MVP (Visual Basic)- Proposed as answer by Riquel I'm Saturday, August 14, 2010 8:00 AM
- Marked as answer by Guang-Ming Bian - MSFTModerator Thursday, August 19, 2010 9:44 AM
Friday, August 13, 2010 6:02 PM
All replies
-
I don't believe that PCOM is a Microsoft product so whether there is a .NET version will depend upon whether one is developed by the vendor (IBM?).
There is nothing that Microsoft can do, alone, to eliminate the need for COM interop with those applications or libraries that implement the COM architecture.
Paul ~~~~ Microsoft MVP (Visual Basic)Friday, August 13, 2010 2:50 PM -
Thanks, Paul. Although I'm still confused. Are you saying the documentation is wrong - ie, that COM Interop won't be replaced with .Net Framework applications? The words in green above are taken directly from the MS documentation for visual studio. I just don't want to have to convert all my code again two or three years down the road. How long do you estimate COM Interop will be available for vb.net? (IE, how long is the "until then"?)Friday, August 13, 2010 3:32 PM
-
I think what they mean is that COM libraries will be replaced by .NET Framework equivalents over time. It's not going to happen all at once. There is no light switch. Once again, this will depend upon Microsoft and third-party vendors to develop .NET replacement libraries and in some cases it probably will never happen.
There have been no plans or announcements that I am aware of to drop COM interop support from Visual Studio and I would sincerely doubt, since it's still rather prevalent, that it would be dropped anytime in the near future. I would expect that there will be less emphasis on COM interop as apps move to the 64-bit world and legacy 32-bit COM heads towards obsolescence, but I think 32-bit apps will be around for a while yet.With respect to PCOM, IBM would be your best source for support. I don't know what their plans are for .NET.
Paul ~~~~ Microsoft MVP (Visual Basic)- Proposed as answer by Riquel I'm Saturday, August 14, 2010 8:00 AM
- Marked as answer by Guang-Ming Bian - MSFTModerator Thursday, August 19, 2010 9:44 AM
Friday, August 13, 2010 6:02 PM -
Thank you for your reply, Paul. And thank you for explaining this in language that even a "newbie" (I think that's the right term) like me can understand. Much appreciated.Friday, August 13, 2010 7:24 PM