Adobe Plug_ins
Hi,
I have recently snapshot a few apps, that the msi puts additional plug-ins to Adobe Reader 7 (as Reader 7.0 is standard on our builds).
Therefore on my msi, as well as having the files and regkeys for the application, it adds file to “Program files, Adobe, Acrobat 7.0, reader, Plug_ins.â€Â
Looking ahead, when our client no longer includes Acrobat 7.0, but maybe Acrobat 8.0 etc, the app will no longer integrate with Adobe, as the plug in will be in the wrong folder.
I was wandering best way to get around this. A script to look what Adobe version exists?
Cheers,
Mike.
I have recently snapshot a few apps, that the msi puts additional plug-ins to Adobe Reader 7 (as Reader 7.0 is standard on our builds).
Therefore on my msi, as well as having the files and regkeys for the application, it adds file to “Program files, Adobe, Acrobat 7.0, reader, Plug_ins.â€Â
Looking ahead, when our client no longer includes Acrobat 7.0, but maybe Acrobat 8.0 etc, the app will no longer integrate with Adobe, as the plug in will be in the wrong folder.
I was wandering best way to get around this. A script to look what Adobe version exists?
Cheers,
Mike.
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
turbokitty
17 years ago
In Installshield, you could use the System Search Wizard to look for the adobe 8.0 folder. You could set that as an install condition on a component that drops the files in the 8.0\plugins folder.
So basically you'd have, for example, three components that each contain the same plugins but pointed at different file locations depending on the version of adobe (6,7,8).
Not sure if you can do that in Wise.
So basically you'd have, for example, three components that each contain the same plugins but pointed at different file locations depending on the version of adobe (6,7,8).
Not sure if you can do that in Wise.
Posted by:
rpfenninger
17 years ago
Since SystemSearch (or AppSearch) is an MSI function, you can do this in Wise as well. Either through Installation Expert, System Search or by directly editing the AppSearch table.
You only need one component (depending on the file types) to accomplish this. The installation directory of that component can be set to check for the Property (the plugin directory in your case) you defined in AppSearch.
You only need one component (depending on the file types) to accomplish this. The installation directory of that component can be set to check for the Property (the plugin directory in your case) you defined in AppSearch.
Posted by:
turbokitty
17 years ago
Ah smart.. I didn't think of that. Yes.. one component.
System Search is different than App Search in Installshield. System Search is a wizard that populates the AppSearch, Signature and locator tables. Wise will of course have AppSearch, just wasn't sure if they had a dandy wizard to accomplish that task.
System Search is different than App Search in Installshield. System Search is a wizard that populates the AppSearch, Signature and locator tables. Wise will of course have AppSearch, just wasn't sure if they had a dandy wizard to accomplish that task.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
