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
- :
- Trying to Extract COM Information
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
‎Nov 14, 2008
04:54 PM
Trying to Extract COM Information
I've been trying to get COM information to extract out of one the DLLs in my Installshield project so that I can include the information in the install rather than having to run regsvr32 on the DLL in a CustomAction.
The Installshield UI doesn't properly refresh the information from the DLL when I go to Advanced Settings-->COM Registration -->Refresh COM Data for Key File.
When I use RegSpyUI.exe to try and look at the DLL, I get an error "ISRegSpy.exe - Entry Point Not Found - The procedure entry point SHGetKnownFolderPath could not be located in the dynamic link library SHELL32.dll".
I'm running IS 2009 on XP SP3, could anyone help me with this error?
The Installshield UI doesn't properly refresh the information from the DLL when I go to Advanced Settings-->COM Registration -->Refresh COM Data for Key File.
When I use RegSpyUI.exe to try and look at the DLL, I get an error "ISRegSpy.exe - Entry Point Not Found - The procedure entry point SHGetKnownFolderPath could not be located in the dynamic link library SHELL32.dll".
I'm running IS 2009 on XP SP3, could anyone help me with this error?
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 17, 2008
10:24 AM
I'd suggest checking the dependencies of that .dll using dependency walker. SHGetKnownFolderPath is only available on Vista (per MSDN), and if I'm reading your message correctly, the problem is the .dll requires that API to be available when you load the .dll server.
If your product requires Vista, this is fine, but COM extraction of this .dll will fail anywhere before Vista. If your product doesn't require Vista, this may need to be fixed by the developers of the errant .dll file.
If your product requires Vista, this is fine, but COM extraction of this .dll will fail anywhere before Vista. If your product doesn't require Vista, this may need to be fixed by the developers of the errant .dll file.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 17, 2008
04:35 PM
Thank you.
This appears to have been the problem. When I extracted the COM info on Vista, everything appears to have worked just fine.
This appears to have been the problem. When I extracted the COM info on Vista, everything appears to have worked just fine.
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)