You are not logged in. You can browse in the PowerBASIC Community, but you must click Login (top right) before you can post. If this is your first visit, check out the FAQ or Sign Up.
In certain type libs you'll find the Version dependent ProgId's. When I create a
COM class, I don't have them. What am I doing wrong.
Also taking as an example the GlossaryServer.dll has a tlb file. When I register the server with regsvr32 and then look it up in the COM browser there is a problem. The COM is unable to access the typelib.
Furthermore, the GlossaryServer doesn't have the ProgID either in the typelib.
I havn't looked at this from the PB side yet at all, but in working from the C/C++ side, a typelib isn't automatically created when a COM component is registered in the Windows Registry by the regsvr32 >> DllRegisterServer() implementation. I'm speaking in C now - if you want to have a type lib created and registered one runs a midl session on the interface definition file specifying the 'library' keyword there as well as other items that go in the typelib. Then, within the COM component in the DllRegisterServer() implementation is a call to LoadTypeLibEx() which causes the *.tlb file creaed by the midl compiler to be registered in the registry. As I said, I havn't as of yet looked at this from the PB side of things to see how its done. But yes, every useable component registered with Windows might not have a type lib associated with it - as far as I know.
Last edited by Fred Harris; 21 Aug 2008, 08:33 AM.
In certain type libs you'll find the Version dependent ProgId's. When I create a
COM class, I don't have them. What am I doing wrong.
Also taking as an example the GlossaryServer.dll has a tlb file. When I register the server with regsvr32 and then look it up in the COM browser there is a problem. The COM is unable to access the typelib.
Furthermore, the GlossaryServer doesn't have the ProgID either in the typelib.
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, and to analyze site activity. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.
Leave a comment: