Software Deployment

In order for selfreg to work, the file must be 'executable' and contain the DllRegisterServer entry point. So if Regsvr32 <filename> doesn't work, then selfreg won't work.

Just as an aside, it's bad practice to use selfreg as the MSI will not contain all the registry entries which than makes for a very poor chance of detecting 'conflicts'

Hi,
Thanks for your reply
yes I am aware that use of selfReg table have some disadvantages.I have a vendor msi in which they have put one tlb and one .vbx file in the selfreg table.When I try to install that vendor Msi...it gives me the error message during instllation.By looking at the log file...i came to know that it fails at registering tlb and Vbx file.

Do you have any idea that whether these (.vbx and .tlb) file can be selfreg using selfreg table?

thanks
Mayur

try registring these files using Regsvr32.exe and see. it they dont have DllRegisterServer entry point then they wont be getting registered. so in this case make sure that these files are not added to selfreg table to ensure the proper installation of your msi

thanks

vbx's are really old 16 bit windows components (prior to ActiveX) and don't need to be registered.

tlb's are 'Type Libraries' and these DO require registration. I'm not sure whether the MSI selfreg table copes with these. To see whether it may be possible there's a RegTlib tool (from Microsoft) you can use - if this recognises the .tlb file, then selfreg may possibly work...