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
- :
- Strange COM Data Extraction issue
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
‎Dec 17, 2008
07:38 AM
Strange COM Data Extraction issue
Dear all!
I'm really experiencing some strange COM Data Extraction issues...
I just created a test-project with my DLL-file and all of its dependend files (all separate components). The dependent files are *.bpl files from borland.
Now here's what i do:
1. After i created all the components i choose to Extract COM Data from the DLL file and everything works perfectly!
2. BUT: If i close the project, reopen it and do the above step again nothing happens. And here's the funny thing: if I delete any of the dependent files and readd it, COM Extraction works again...... Until i close the project and reopen it....
Has anybody experienced this behaviour before??
Michael
I'm really experiencing some strange COM Data Extraction issues...
I just created a test-project with my DLL-file and all of its dependend files (all separate components). The dependent files are *.bpl files from borland.
Now here's what i do:
1. After i created all the components i choose to Extract COM Data from the DLL file and everything works perfectly!
2. BUT: If i close the project, reopen it and do the above step again nothing happens. And here's the funny thing: if I delete any of the dependent files and readd it, COM Extraction works again...... Until i close the project and reopen it....
Has anybody experienced this behaviour before??
Michael
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 17, 2008
05:22 PM
Perhaps it's a matter of the process's current directory? Try creating a new shortcut to InstallShield with the directory those files are in and let us know if it fixes it. Another thing you could try is registering the dependencies on the machine before trying to run COM extraction.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 19, 2008
05:59 AM
Michael you're a genius!
IT WORKED! 🙂
I just created a shortcut to the InstallShield-EXE and set the "Start in" directory to the path of my setup-files.
Do you think there will be a hotfix for this issue?
IT WORKED! 🙂
I just created a shortcut to the InstallShield-EXE and set the "Start in" directory to the path of my setup-files.
Do you think there will be a hotfix for this issue?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 19, 2008
09:58 AM
I'm glad changing the directory worked for you. Until I know more about why this is a problem, I can only guess as to a hotfix, and this hasn't come up much. Is it possible that the DLL or EXE you are COM extracting is loading its dependencies in an unusual fashion?
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)