Hello,
I found the following post in Google Groups:
I have a shared COM Dll and I created a merge module for this.
I have two features will consume this module.
The final result is:
always the first feature gets correct registration for this COM Dll.
Example:
Both features include this COM Dll merge module.
1. Install only Feature1. OK
2. Install both Feature1 and Feature2. OK
3. Install only Feature 2. Fail.
...
I've got the same problem but could not find a solution.
Is there a solution or a workaround?
I use Installshield Developer German 7.03
Thanks for your help.
This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
COM Dlls are not got registered correctly
Started by
Pro2
, Jul 04 2002 10:07
1 reply to this topic
bholz
-
- Members
- 12 posts
Posted 20 December 2002 - 10:14
Hi,
I have got the same problem and found the cause:
In the class table the CLSID is bound to the feature being installed. So only if the selected feature is installed, the COM server gets registered correctly.
By now I found no way to get around this. I see two approaches:
1. Use COM server self registration. I dont want to do this.
2. Put the com server in its own (hidden) feature any manage dependencies by hand. I dont know how to do this. I guess I should take a closer look at the feature conditions.
Regards,
Bernd
I have got the same problem and found the cause:
In the class table the CLSID is bound to the feature being installed. So only if the selected feature is installed, the COM server gets registered correctly.
By now I found no way to get around this. I see two approaches:
1. Use COM server self registration. I dont want to do this.
2. Put the com server in its own (hidden) feature any manage dependencies by hand. I dont know how to do this. I guess I should take a closer look at the feature conditions.
Regards,
Bernd