Adobe InDesign for different customers
Hello everybody,
I have a small packaging project in my queue and looking for the best way to do it.
Basicly the whole installation is splitted into Adobe InDesign itself, a plugin for InDesign and an additional program, furthermore some xml files have to be changed and a few files have to copied from A to B...
My question is: Can I add some kind of VBS Script to the package I create which will be executed after the installation and can perfom the changes in the xml files?
Furthermore a more general thing I need to know:
I know how to package in an enterprise environment from my time as a trainee, but this package should be used at different customers at the end. How do I package here? Also "Setup Capture" or is there another (better) way?
Many thanks for your help in advance...
bgi
I have a small packaging project in my queue and looking for the best way to do it.
Basicly the whole installation is splitted into Adobe InDesign itself, a plugin for InDesign and an additional program, furthermore some xml files have to be changed and a few files have to copied from A to B...
My question is: Can I add some kind of VBS Script to the package I create which will be executed after the installation and can perfom the changes in the xml files?
Furthermore a more general thing I need to know:
I know how to package in an enterprise environment from my time as a trainee, but this package should be used at different customers at the end. How do I package here? Also "Setup Capture" or is there another (better) way?
Many thanks for your help in advance...
bgi
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
Rheuvel
13 years ago
In the case of Adobe products, I'd use their own tooling to create a package. Have a look at the Package KB, check the version of InDesign you want to deploy (possibly listed just under Creative Suite version x) and use the info there.
Posted by:
anonymous_9363
13 years ago
Although the 'Package KB' describes the installer as 'Legacy', the Notes therein clearly show '/QB' being passed on the command line so one assumes that there is an MSI being extracted. Thus, you can build transforms to accomodate your different targets. Some Adobe products have a specific tool for customisation: check the Adobe site to see if there's one for InDesign.
For XML changes, I would recommend avoiding simply search-and-replace in VBS. Get hold of an XML class (I think I may even have posted one here in a fit of generosity) or use the Chilkat XML control (free, last time I checked).
For XML changes, I would recommend avoiding simply search-and-replace in VBS. Get hold of an XML class (I think I may even have posted one here in a fit of generosity) or use the Chilkat XML control (free, last time I checked).
Posted by:
bgi
13 years ago
Thanks so far guys,
For the adobe indesign I really hope to get this covered with the Adobe Deployment Toolkit
The chillkat XML stuff is still free, good idea btw...
But I need more "startup help" at the moment...is it possible to repackage a exe file and add a script to the msi which runs after the installation? Is it possible to repackage in this case (because the package should be installed at different customers)?
My first approach was to realise it in Auto IT but I would prefer to have msi files...
For the adobe indesign I really hope to get this covered with the Adobe Deployment Toolkit
The chillkat XML stuff is still free, good idea btw...
But I need more "startup help" at the moment...is it possible to repackage a exe file and add a script to the msi which runs after the installation? Is it possible to repackage in this case (because the package should be installed at different customers)?
My first approach was to realise it in Auto IT but I would prefer to have msi files...
Posted by:
anonymous_9363
13 years ago
Do NOT repackage, especially not Adobe products.
Extract the MSI and use the appropriate deployment toolkit to create a transform.
Extract the MSI and use the appropriate deployment toolkit to create a transform.
Posted by:
bgi
13 years ago
your right! as far as I know the Adobe stuff writes their MSIs in the temp folder...I really hope the plugins do the same.
Thanks so far guys, I will keep you posted...
Thanks so far guys, I will keep you posted...
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.