Thanks for replying, Bruce.
I've downloaded Manifest Maker evaluation and am trying to understand it but it's not yet working as expected. I'll persevere...
OK I see that the manifest for the component must be <file name>.dll.manifest. I had <file name>.manifest so I'll fix that.
I'm still not clear on the clSid. When I create a component in PB .net where does the clSid come from?
As far as I can see the first time I become aware of what it is is when regasm creates a .reg file which exposes the clsid. If I do not plan to use regasm then how do I discover the clsid to put into the manifest?
When building the PB Classic project do I use the 'No manifest' option?
TIA
Larry