By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,631 Members | 1,144 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,631 IT Pros & Developers. It's quick & easy.

PROBLEM: Dynamically reference different versions of the same COM dll's

P: n/a

I have the following situation:

I have a COM enabled application installed on multiple machines. I'm
building a management application for the COM application. Normaly this is
very easy as the .Net framework can create an interop for you which you can
use in your project.

The problem I'm facing is that the COM enabled application can be several
different versions! The set of exposed classes is identical, but some
classes have different api's in different versions of the COM dll. Some new
methods or properties can be added or some old ones can be removed. I'm only
interested in the mutual set of methods and properties.

As you can image I can not create one interop and use it accross all the
different COM dll versions as the implemented API might not be compatible.
Errors like 'A null reference pointer was passed to the stub' are already
common to me. I have also played a little with ILDASM tool, but have not
found an answer there yet.

What I'm looking for, is the right approach to this problem. Is there a way
to create an interop for just the mutual set of properties and methods and
use that in my project? Anyone got any pointers?

Kind regards,
Nov 17 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.