Keeping VB Components Compatible


If you have been involved in even a moderately sized Visual Basic project, then you undoubtably have run into issues associated with maintaining compatibility between different versions of your ActiveX components. While it seems like this should be a simple concept, the details require an understanding of some of the 'guts' of COM object plumbing. Not for the faint of heart. In this article, we discuss these details and walk you through the process of determining what compatibility setting is best suited for your project.

As a starting point, compatibility is only an issue if you're creating an ActiveX DLL. If all of your classes fit inside one single executable, then compatibility will not come into play. Once you have created your new project, select Project | Project Properties and select the Component tab. At the bottom of the dialog box, you can select from No Compatibility, Project Compatibility and Binary Compatibility. If you specify Binary Compatibility, you must also provide the path to an existing component to act as the base for the interface. But more on that later.

You might also like...


About the author

Bruce Johnson Canada

I am the owner of a small application development consulting company that specialized in the design and implementation of Internet-based applications. While there are others who can make a web ...

Interested in writing for us? Find out more.


Why not write for us? Or you could submit an event or a user group in your area. Alternatively just tell us what you think!

Our tools

We've got automatic conversion tools to convert C# to VB.NET, VB.NET to C#. Also you can compress javascript and compress css and generate sql connection strings.

“Anyone who considers arithmetic methods of producing random digits is, of course, in a state of sin.” - John von Neumann