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
- :
- Where are the dependencies
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page

Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 12, 2011
07:36 AM
Where are the dependencies
I am using VS2010 and have just installed InstallShield LE. I have followed the instructions for scanning the depencies i.e. right-click on the project primary output and select Dependencies from Scan at build... The resulting form shows a list of my dependencies, all selected and I click Ok. What happens to them after that? When I build, the builder complains that the depencies are missing. Can anyone please advise,
Many thanks.
Many thanks.
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 27, 2011
01:14 AM
I have the exact same issue. I found a thread which someone mentioned a workaround to select properties on the file with the dependencies, then under COM & .NET Scan at Build to change to Properties Only. This seems to satisfy the compiler, but unfortunately when installing the end product on another PC, it fails to run with an File Not Found exception for the dependant DLL. Looking forward to a resolution on this one.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 09, 2011
06:28 AM
Hi,
To overcome this error you have to either add the dependent file to the Primary Output location or add a Reference to their Visual Studio project to the dependent file using Visual Studio’s Solution Explorer.
Thanks,
Madu
To overcome this error you have to either add the dependent file to the Primary Output location or add a Reference to their Visual Studio project to the dependent file using Visual Studio’s Solution Explorer.
Thanks,
Madu
