Automation Build in installshield
-
I have done this. I will dig out some notes. Its not too hard, but you do need to test the steps - Badger 9 years ago
Answers (4)
(please google for description of the rest of them :)
ISWiAdvancedFile Object
ISWiAutomaticUpgradeEntry Object
ISWiCustomAction Object
ISWiComponent Object
ISWiComponentSubFolder Object
ISWiCondition Object
ISWiDimDependency Object
ISWiDimReference Object
ISWiDynamicFileLinking Object
ISWiEnvironmentVar Object
ISWiFeature Object
ISWiFile Object
ISWiFolder Object
ISWiLanguage Object
ISWiObject Object
ISWiPathVariable Object
ISWiProductConfig Object
ISWiProperty Object
ISWiRelease Object
ISWiSequenceRecord Object
ISWiSetupFile Object
ISWiSetupType Object
ISWiShortcut Object
ISWiSISProperty Object
ISWiSQLConnection Object
ISWiSQLDatabaseServer Object
ISWiSQLReplace Object
ISWiSQLRequirement Object
ISWiSQLScript Object
ISWiStringEntry Object
ISWiUpgradeTableEntry Object
And check some tips and C# code here:
http://stackoverflow.com/questions/13814473/programatically-create-installshield-packages
Comments:
-
I Dont know how to use ISWIProject object.. - perumal9791 9 years ago
Last time I did this (best job ever!!)
We used the iscmdbld.exe. I wont give you the full answer, but have a look at the cmd arguments and you should be OK.
You say your searches are not giving you what you want??? What exactly do you want??
You run the build by using the iscmdbld.
you have to have your ISM. I would recommend setting up a release in that first.
What files are you trying to add automatically???
Create the ism, use relative paths, it will add the files in as you go. If you are writing code, building that into binaries for a products, if you add a new binary file, you will have to add that into the MSI via the ISM in a component, associated with a feature.
Oh, free tip. save the ISM in XML format. That will be handy later on in ways you cant imagine now.