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: Automatically add newly added files from source folder into Installshield Project
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
Oct 24, 2017
08:22 AM
Automatically add newly added files from source folder into Installshield Project
Dear All,
My requirement is as below :
- My project is installshield standard msi project. It has got component under a feature.
- Whenever developers add a project to product a new DLL is added into source folder.
- With current process I manually create a component and add this new DLL into project.
Is there any mechanism in installshield which can create a component per file and only add newly added files from source folder in my installshield project? I tried dynamic file linking, but it fetches all files which is not my requirement.
Thanks in advance.
Amarjeet
My requirement is as below :
- My project is installshield standard msi project. It has got component under a feature.
- Whenever developers add a project to product a new DLL is added into source folder.
- With current process I manually create a component and add this new DLL into project.
Is there any mechanism in installshield which can create a component per file and only add newly added files from source folder in my installshield project? I tried dynamic file linking, but it fetches all files which is not my requirement.
Thanks in advance.
Amarjeet
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Oct 26, 2017
05:27 PM
You could still use the dynamic file links by adding an exclude filter. Its at the bottom of the dynamic file link settings window. Or you could add an include filter of *.dll
I would caution you though that binaries should have their own components and be the key file of those components. Using a dynamic link like this would not follow that rule.
I would caution you though that binaries should have their own components and be the key file of those components. Using a dynamic link like this would not follow that rule.