Versioning Rules for COM

Do anyone producing in-house software follow the versioning rules for COM? 

anon
Wednesday, May 12, 2004

Nope. The COM versioning rules, such as they were, never seemed to work right in practice. Plus add VB to the mix and everything got screwed up.

Chris Tavares
Wednesday, May 12, 2004

What "versioning rules for COM" are you referring to?

Do you mean PROGIDs, in both version dependent and independent form? If so, then yes, I've used them and they work just fine. So does Microsoft. So, maybe you can be more specific?

Brad Wilson (dotnetguy.techieswithcats.com)
Wednesday, May 12, 2004

I'm guessing that he is referring to the "rules" about major and minor release numbers. Most shrink wrap software packages do a good job. I, on the other hand, usually only worry about changing major release numbers if I'm forced to break an interface. My users (me, myself, and I) never seem to complain too loudly.

Rob VH
Wednesday, May 12, 2004

As far as I know, the only versioning rule for COM is that you change the GUID (either CLSID or IID) if you break compatibility. And far too many developers thought that they didn't break compatibility when they actually did.

Chris Tavares
Thursday, May 13, 2004

  Recent Topics

  Fog Creek Home