Hello, I work on a project that will be shipped to customers one day, but I don't want to give out any sources. One approach to make the interfaces available to them is to build special server dll's that house no coclasses but implement Dll[Un]RegisterServer. This way our customers only need to #import these dll's and have access to all necessary interfaces. Is this technique common? Is there a name for this technique that is known in COM society? Thanks in advance, Stuart
The typelibrary holds this information. /Helge
Helge Kruse wrote: > > The typelibrary holds this information. > > /Helge Okay, but my question is about how I distribute the type library. One would be to ship a .tlb-file, but I prefer to ship the type library as DLL. Is there a widely known name for such a kind of DLL that contains only type libraries?
See regtypelib. If you want to ship a DLL, change the extension from TLB to DLL. regtypelib doesn't care. Brian "Stuart Redmann" wrote in message news:437DDBC7.F0D2B2B7@web.de... > Helge Kruse wrote: >> >> The typelibrary holds this information. >> >> /Helge > > Okay, but my question is about how I distribute the type library. One > would be to ship a .tlb-file, but I prefer to ship the type library as > DLL. Is there a widely known name for such a kind of DLL that contains > only type libraries?
You can call it advertising, or stub DLL. In addition you can implement DllGetClassObject to show some advertising message when a class object is requested. Microsoft Office works that way. If you want to make your customers life easy, you can provide some dummy interface implementation which will, for example, write name of the function called to log. It will give possibility not only to import and compile, but also to run and test using this dummy dll. "Stuart Redmann" wrote in message news:437D8F67.F9775712@web.de... > Hello, > > I work on a project that will be shipped to customers one day, but I > don't want to give out any sources. > One approach to make the interfaces available to them is to build > special server dll's that house no coclasses > but implement Dll[Un]RegisterServer. This way our customers only need to > #import these dll's and have access > to all necessary interfaces. Is this technique common? Is there a name > for this technique that is known in > COM society? > > Thanks in advance, > Stuart
