Registering Dll's/ocx's
Hi all!
I was wondering what the best way is to register a few DLL's.
I have a custom package with some dll's and an few ocx's. Need to overwrite some dll's
on the workstation, and they need to get registered. What the best way to do this..? Use Wisecomcapture (read about that in a thread on the board somewhere) and extract the registry information, or register the dll's through custom actions (regsvr32 <dll>) in the MSI? Thanks!
I was wondering what the best way is to register a few DLL's.
I have a custom package with some dll's and an few ocx's. Need to overwrite some dll's
on the workstation, and they need to get registered. What the best way to do this..? Use Wisecomcapture (read about that in a thread on the board somewhere) and extract the registry information, or register the dll's through custom actions (regsvr32 <dll>) in the MSI? Thanks!
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
aogilmor
17 years ago
Posted by:
neo2000
17 years ago
Ok, thanks..! I'm using Wise 6.. I already figured out they were registered al by them selves. Didn't know Wise did that.. [:)]
Anjd now the million dollar question.. Any option to turn this off in Wise..? Is it the "automatically add self registration" option in Wise..? Or just remove the files from the selfregister table?
I need to get a some DLL files in the package registered, and one DLL outside of the package, already on the workstation. The one outside of the package must not be un-registered on uninstall. Going to have to fiddle with it some more i guess..
Anjd now the million dollar question.. Any option to turn this off in Wise..? Is it the "automatically add self registration" option in Wise..? Or just remove the files from the selfregister table?
I need to get a some DLL files in the package registered, and one DLL outside of the package, already on the workstation. The one outside of the package must not be un-registered on uninstall. Going to have to fiddle with it some more i guess..
Posted by:
AngelD
17 years ago
I wouldn't use the SelfReg table as this would be the same as register with regsvr32.exe, they use the same functions to register or unreg the file.
I usually add COM component register information in the Class/ProgId/TypeLib tables and Registry table as it's safer then using regsvr32 or SelfReg tabel and you will not have to think about the register order for any of the COM component as this will not be required when you dont use the SelfReg table.
Yes, by un-checking the "automatically add self registration" option no file will get into the SelfReg table.
In my own experience I think Regspy.exe works better then WiseComCapture.exe does.
You can find Regspy.exe from the The Definitive Guide to Windows Installer - Source Code in the Chapter03\Regspy directory.
I usually add COM component register information in the Class/ProgId/TypeLib tables and Registry table as it's safer then using regsvr32 or SelfReg tabel and you will not have to think about the register order for any of the COM component as this will not be required when you dont use the SelfReg table.
Yes, by un-checking the "automatically add self registration" option no file will get into the SelfReg table.
In my own experience I think Regspy.exe works better then WiseComCapture.exe does.
You can find Regspy.exe from the The Definitive Guide to Windows Installer - Source Code in the Chapter03\Regspy directory.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.