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
- :
- New standard dll located in search path
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
Aug 05, 2009
07:50 AM
New standard dll located in search path
Did anybody used this Custom Action before?
(New standard dll located in search path)
I am searching for a dll on the target computer, using SystemSearch:
AppSearch Action found:
[MYFILEEXISTS]='c:\mydll.dll'
Then, I used a Custom Action to access that dll:
Dll Filename = mydll.dll
Function Signature = void mydll::MyFunc()
At install time, I get a message, that mydll.dll is not found.
Do you have any clues of how this CA's are working?
Thanks
(New standard dll located in search path)
I am searching for a dll on the target computer, using SystemSearch:
AppSearch Action found:
[MYFILEEXISTS]='c:\mydll.dll'
Then, I used a Custom Action to access that dll:
Dll Filename = mydll.dll
Function Signature = void mydll::MyFunc()
At install time, I get a message, that mydll.dll is not found.
Do you have any clues of how this CA's are working?
Thanks
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Aug 05, 2009
11:52 AM
This issue is typically caused by missing dependencies required to successfully load the custom action DLL. The Windows LoadLibrary API reports a generic "file not found" error and therefore this is the error displayed by the standard DLL wrapper.
Information on troubleshooting this issue can be found in the following article:
Q112128: INFO: Troubleshooting Failures Of DLL Custom Actions
Information on troubleshooting this issue can be found in the following article:
Q112128: INFO: Troubleshooting Failures Of DLL Custom Actions