COM or no COM

[Shreenivas]

While migrating from vb6 to vb.net we are offered a choice to use COM or not (i.e. use SS??? components).

1) What should be the deciding criteria?

2) Would the interop components work on 64bit Windows 10 professional?

 

[OlmanQuesada]

Hi,

The Visual Basic Upgrade Tool (VBUC for short) support the conversion of some COM/Activex components to .Net equivalents, however, it's possible some properties or methods may not be supported in .Net.

At the end of the day an Activex is not a .Net component and given that VS.Net creates an interop wrapper to communicate the .Net Framework with the COM component in practice, some functionality of the Activex could cause memory-leaks. It is also possible some component design properties are not accessible in .Net.

In regards with your second question, for a COM / Activex component to work in .Net, the in application must be compiled in 32 bits. If you want to have a 64bits app, yuou need to replace all COM functionality by .Net.

Please let me know if you have any other question.

OlmanQ

[Shreenivas]

Thanks. This mostly answers the questions.

You mentioned that the interop may bock some of tbe properties and functionality of the original Active-X. Does it also mean that the .Net equivalents are designed to retain all the properties and functionality of the original Active-X?

[John Browne]

As Olman said above, not all properties, methods, or events from ActiveX components are guaranteed to be supported by newer, equivalent classes in .NET