< Is COM actually worth it > ?

[RichardF]

Hi,

We are experiencing some difficulties with programs that use constantly evolving com objects.

Some programs use this copy, some programs use that copy, etc. It seems to be very hard to keep everything 'in line' whilst progressing the com object.

now, our managers are getting tired and *demand* that we start using version numbers inside the filenames. like myocx1_0.ocx, myocx1_1.ocx.

Is this overkill ?

Any ideas ?

 

[chiph]

We use version names so that we're able to run two versions of the component on the same server. You need to change the ProgID as well as the filename (I recommend you make them the same, keeping an eye on the 39-character limit for a ProgID).

The other thing we do is use constants inside our code:

[tt][tab]Public Const PROGID_UTILITY_NETWORK As String = "pcUtility43.Network"[/tt]

So that we only have to update it in one place when we want to point the code at the newer version.

Chip H.