This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Self-registerable files
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 07, 2008
03:08 PM
Self-registerable files
Hi, this is probably the dumb question of the day, but here goes: I have several DLL and OCX files that are self-registerable, and have set the Self-Register Property in the IDE Setup to Yes for all self-registerable DLL and OCX files under this particular Component. Is it also necessary for me to run something like LaunchAppAndWait (WINSYSDIR ^ "regsvr32.exe", + , WAIT) in the InstallScript of this project, or is that redundant? I understand that certain factors could cause the self-register process to fail during install (e.g. file(s) in use), but aside from that this is what I need to know. Many thanks.
Regards,
Randy
Regards,
Randy
(5) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 07, 2008
04:04 PM
It's redundant. If you know that DllRegisterServer() calls increase installer fragility, why are you using it? Is there really a reason why you can't right click | Extract COM the keyfile of the component or use COM Extract at Build?
I fought the concept of "COM Extraction Is Best Practice" for about the first 12 months I wrote Installs. Eventually I came to be a believer and I hope you will also.
I fought the concept of "COM Extraction Is Best Practice" for about the first 12 months I wrote Installs. Eventually I came to be a believer and I hope you will also.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 07, 2008
04:23 PM
If you're using an InstallScript project, though, those don't have COM extraction. Chris is quite right, though, that you don't need to double-register your self-registering files.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 07, 2008
04:34 PM
First, I apologize if I assumed incorrectly that you are using an MSI project.
Second, hmmm, I wonder.... Why not use MSI-style DLL registration in InstallScript projects?
I once wrote a `fake` installer for an Airline Terminal Emulator ( Attachmate WRQ/InfoConnect now owned by TCB also ). The requirement was that all applications had to be applied isolated to the user profile when an airline loggen in and when the user logged off, it had to be back to the exact same pristine state.
This was accomplished by running the application off of the network and applying all COM/Registry to the HKCU hive with only a couple HKLM\SOFTWARE\Attachmate keys. All user documents were to the profile and when the user logged off, it was all backed out so that when another airline logged in it wouldn't conflict with their product.
But what does this have to do with SelfReg? Imagine running a registry snapshot/diff tool to come up with a Reg file for do/undo instead of calling regsvr32 for 100+ DLL's. The perfomance difference is amazing and it's more reliable.
So maybe a neat feature for InstallScript would be a lighter weight COM registration pattern.
Second, hmmm, I wonder.... Why not use MSI-style DLL registration in InstallScript projects?
I once wrote a `fake` installer for an Airline Terminal Emulator ( Attachmate WRQ/InfoConnect now owned by TCB also ). The requirement was that all applications had to be applied isolated to the user profile when an airline loggen in and when the user logged off, it had to be back to the exact same pristine state.
This was accomplished by running the application off of the network and applying all COM/Registry to the HKCU hive with only a couple HKLM\SOFTWARE\Attachmate keys. All user documents were to the profile and when the user logged off, it was all backed out so that when another airline logged in it wouldn't conflict with their product.
But what does this have to do with SelfReg? Imagine running a registry snapshot/diff tool to come up with a Reg file for do/undo instead of calling regsvr32 for 100+ DLL's. The perfomance difference is amazing and it's more reliable.
So maybe a neat feature for InstallScript would be a lighter weight COM registration pattern.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 08, 2008
11:32 AM
Hi, first of all, thanks to both of you for your prompt and helpful replies. And my apologies, I should have specified that this is an InstallScript-based project. But I like the idea of having a reg file for undo/do, instead of multiple calls on regsvr32! Thanks again, very much appreciate your replies. Cheers.
Randy
Randy
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 12, 2008
01:43 PM
How do I know whether the dll I want registered is self-registering or not?
If it isn't, should I go ahead and use regsvr32 in my installscript? I didn't quite understand what to do otherwise.
If the dll is self registering, other than installing the dll, is there something else I need to do?
Thanks!
B
If it isn't, should I go ahead and use regsvr32 in my installscript? I didn't quite understand what to do otherwise.
If the dll is self registering, other than installing the dll, is there something else I need to do?
Thanks!
B
![](/skins/images/8C9D13A71C7F7695F3262372C0172D68/responsive_peak/images/icon_anonymous_message.png)