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
- :
- Re: VS2012: IS LE 2013: Dependent assemblies copied only once
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 20, 2013
09:54 AM
VS2012: IS LE 2013: Dependent assemblies copied only once
Hi,
Facing an issue with IS LE 2012 Spring & 2013 LE as well. I have VS 2012 solution with one common project (A) and several projects (B, C, D etc..,) referencing the common project. When I add a IS setup project and include project B's primary output, a setup file is created with project B's output and also project A's output. This is perfectly fine. But when I starting adding different folders within the same setup project to include project C & D's output, the output of the common project is copied to ONLY one of the projects whereas the expected behavior is to have the common projects output to all the projects that are referring it.
When I remove the project that has project A's output from setup and build again, project A's output magically appears in some other project's output. It appears that IS has some sort of flag to the files that needs to be copied and ignore the file it is copied to one location?
The dependency scan on each project's output seems to show all the files correctly but misses them when it is copied over. I even tried adding the common project's (proj A) primary output to all other projects that are referring it but still the assemblies are not copied over.
Any suggestions?
Facing an issue with IS LE 2012 Spring & 2013 LE as well. I have VS 2012 solution with one common project (A) and several projects (B, C, D etc..,) referencing the common project. When I add a IS setup project and include project B's primary output, a setup file is created with project B's output and also project A's output. This is perfectly fine. But when I starting adding different folders within the same setup project to include project C & D's output, the output of the common project is copied to ONLY one of the projects whereas the expected behavior is to have the common projects output to all the projects that are referring it.
When I remove the project that has project A's output from setup and build again, project A's output magically appears in some other project's output. It appears that IS has some sort of flag to the files that needs to be copied and ignore the file it is copied to one location?
The dependency scan on each project's output seems to show all the files correctly but misses them when it is copied over. I even tried adding the common project's (proj A) primary output to all other projects that are referring it but still the assemblies are not copied over.
Any suggestions?
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Feb 07, 2014
06:43 AM
Hi,
Could you please confirm if you have tried adding all the files manually once?
Thanks,
Chaitra
Could you please confirm if you have tried adding all the files manually once?
Thanks,
Chaitra
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)