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
- :
- Re: Com registration
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
‎Jul 23, 2008
04:49 AM
Com registration
Hi
I have an issue with some dll and ocx files that are not registered. Confusion starts when i noticed that on some test machines it registers as it should, while on others they are not.
If i check the logfiles i see that they are simply skipped but no error message is shown.
Some context info:
I copy some DLL and OCX files to a directory under common components, these need to be registered so i use the "extract at build" option.
If i edit the builded MSI, i can see that the Class, ProgID table are populated with the extracted info.
Manual registering the files works fine.
The files are all in separate components and these are attached to only 1 feature.
I have the impression that the registration is not done on machines were an older version of the program was installed and registration of those files were already done (in another location).
I thought that the normal behaviour would be if the files were copied, the registration would always be done. Obviously this is not the case and i don't know the rules of this behaviour and i don't have error messages to start solving this problem.
Is there anyone who can explain the normal behavior and therefor explaining why this is happening?
I have an issue with some dll and ocx files that are not registered. Confusion starts when i noticed that on some test machines it registers as it should, while on others they are not.
If i check the logfiles i see that they are simply skipped but no error message is shown.
Some context info:
I copy some DLL and OCX files to a directory under common components, these need to be registered so i use the "extract at build" option.
If i edit the builded MSI, i can see that the Class, ProgID table are populated with the extracted info.
Manual registering the files works fine.
The files are all in separate components and these are attached to only 1 feature.
I have the impression that the registration is not done on machines were an older version of the program was installed and registration of those files were already done (in another location).
I thought that the normal behaviour would be if the files were copied, the registration would always be done. Obviously this is not the case and i don't know the rules of this behaviour and i don't have error messages to start solving this problem.
Is there anyone who can explain the normal behavior and therefor explaining why this is happening?
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 28, 2008
02:26 AM
It remains painfully quite in this post ... 😞
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 28, 2008
04:20 AM
When you install the application, what are the installed/request/action states of the components?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 28, 2008
07:16 AM
Hi
Coming from the failed register log:
******.dll; Installed: Absent; Request: Local; Action: Local
These states are the same on the machine where the registration of these dll's worked.
Thanks
Coming from the failed register log:
******.dll; Installed: Absent; Request: Local; Action: Local
These states are the same on the machine where the registration of these dll's worked.
Thanks
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 29, 2008
07:34 AM
OK, little update
It seems that the ISCmdBld.exe tool has a problem with this extract com at build option.
We found out that the problems were related to the automated build and if we look at the logs, the extract is not done properly (warning -4354, should be an error in my p.o.v.).
I'm going to search now why, if anyone has experience with this or a decent tip, please post it here.
Thanks in advance.
It seems that the ISCmdBld.exe tool has a problem with this extract com at build option.
We found out that the problems were related to the automated build and if we look at the logs, the extract is not done properly (warning -4354, should be an error in my p.o.v.).
I'm going to search now why, if anyone has experience with this or a decent tip, please post it here.
Thanks in advance.