Jump to content

COM or no COM

Recommended Posts

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?


Share this post

Link to post
Share on other sites


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.


Share this post

Link to post
Share on other sites

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?

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Terms of Use