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
- :
- One component for each dll, AND JAR file?
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 13, 2008
11:38 AM
One component for each dll, AND JAR file?
I always see the statement there should be one component for each dll, ocx, exe as installer check the key file for repair and it is important in that sense to have a component for each dll.
I think this statement should include jar files as well. They are also important and like dll's in a sense. Anybody agrees?
I was planning to dynamically link a folder that contains many jar files and then decided not to, because I saw that when dynamically linked all the jar files are going to same component.
I think this statement should include jar files as well. They are also important and like dll's in a sense. Anybody agrees?
I was planning to dynamically link a folder that contains many jar files and then decided not to, because I saw that when dynamically linked all the jar files are going to same component.
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 13, 2008
11:58 AM
InstallShield 2009 adds support for "best practice" dynamic links, and you can define your own file extensions for which you want separate components under Tools > Options > File Extensions.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 14, 2008
04:08 AM
Thanks, I have now added the jar extension there, but what is the idea of the best practice? Ideally I would expect it to create one component for each jar file. But it is not doing that, it is just creating one component called AllOtherFiles and putting all the files/folders underneath that. This is the same behavior when I try to dynamically link dll files. So best practice is not creating one component for each dll nor jar files.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 14, 2008
08:51 AM
At least for a dynamic link with the best practices option, when you build the project and open the output MSI database, you should see the JAR files (and other extensions listed in the Tools > Options > File Extensions setting) in separate components.
Similarly, if you use the Component Wizard and select the Best Practices option, you should have a new component in your project for each JAR file.
Similarly, if you use the Component Wizard and select the Best Practices option, you should have a new component in your project for each JAR file.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 14, 2008
10:43 AM
Great, thanks. As you said the resulting msi or msm have one component for each jar or dll files although it shows one single component in the ism project with all files underneath. So we are good since the resulting msi or msm have separate components.