views:

21

answers:

0

We have a win32 unmanaged application that has an API we distribute as a type library. Several other applications we build depend on the TLB from the legacy application being registered to build.

Each product is still under active development, including the items exposed/accessible to the type library. While trying to find the best way to manage dependencies on the type library I ran across the question, When To Change a GUID on a Type Library and began to wonder if our complete approach to the type library may need to be visited.

  • What are the best practices for creating and distributing a type library?

  • How are others managing applications that have a dependency on a type library that is being actively developed?

  • Is there a more dependable way other than a COM type library for what we're doing?

Sorry for the barrage of questions, but something smells and I have little experience with COM. Any best practices links are greatly appreciated.

Thanks