Installshield regsvr32 a dll
Hi,
Win 7 - 32\64 bit.
I'm creating an msi to add a dll and register it (regsvr32 /s).
I'm used to using Wise. In Wise I would use wisecomcapture to extract the registry entries and add to the msi.
I'm running repackager in Installshield, am I correct in saying that I only need to:
1) start snapshot
2) copy the file
3) close snapshot
Then in 'Files and folders' - right click the dll (it's a keypath) and select 'Extract COM Data for key file'.
Does selecting 'Extract COM Data for key file' do the same as running regsvr32 during the snapshot? Or do I still need to run regsvr32?
Thanks...
Win 7 - 32\64 bit.
I'm creating an msi to add a dll and register it (regsvr32 /s).
I'm used to using Wise. In Wise I would use wisecomcapture to extract the registry entries and add to the msi.
I'm running repackager in Installshield, am I correct in saying that I only need to:
1) start snapshot
2) copy the file
3) close snapshot
Then in 'Files and folders' - right click the dll (it's a keypath) and select 'Extract COM Data for key file'.
Does selecting 'Extract COM Data for key file' do the same as running regsvr32 during the snapshot? Or do I still need to run regsvr32?
Thanks...
0 Comments
[ + ] Show comments
Answers (7)
Please log in to answer
Posted by:
spartacus
12 years ago
ORIGINAL: VBScab
Using wisecomcapture makes your work easyA little tricky when the OP doesn't own a Wise product...
RegSpyUI.exe which can be found in %ProgramFiles%\InstallShield\2010\Support (for InstallShield 2010) is, broadly speaking, an equivalent tool which will allow you to export the COM registration details of a DLL as a .REG file suitable for import to your package.
Spartacus
Posted by:
SandeepPanat
12 years ago
Which version of InstallShield are you using?
Prior to InstallShield 2011, if UAC is disabled then 'Extract COM Data for key file' had a limitation of not capturing Interface and TypeLib keys.
Prior to InstallShield 2011, if UAC is disabled then 'Extract COM Data for key file' had a limitation of not capturing Interface and TypeLib keys.
Posted by:
pjgeutjens
12 years ago
Easiest solution imo is still to capture the dll registration and add the registry keys to your package directly.
Unless you need advertised entry points on the dll's it will cover your needs just fine.
Kr,
PJ
Unless you need advertised entry points on the dll's it will cover your needs just fine.
Kr,
PJ
Posted by:
Meic
12 years ago
Thanks for your replies.
Using Installshield 2011.
When you say 'easiest solution is still to capture the dll registration and add the registry key to the package directly', do you mean caputre it by running regsvr32 on the dll during capture or by running wisecomcapture?
Thanks.
Using Installshield 2011.
When you say 'easiest solution is still to capture the dll registration and add the registry key to the package directly', do you mean caputre it by running regsvr32 on the dll during capture or by running wisecomcapture?
Thanks.
Posted by:
mahendraKumar
12 years ago
Using wisecomcapture makes your work easy ... i would recommend it ....
Posted by:
anonymous_9363
12 years ago
Using wisecomcapture makes your work easyA little tricky when the OP doesn't own a Wise product...
Posted by:
bandarukishore
12 years ago
I tried to register 64 bit dll using RegSpyUI.exe, it didn't export any COM data information & Created empty .reg file. But it is getting registered with regsvr32.exe Please suggest, Is there any other tool for 64 bit dll or am i missing something to export.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.