Jump to content

This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.

Workaround for missing automation interface features

2 replies to this topic


  • Full Members
  • 47 posts

Posted 07 June 2013 - 15:35

Hi there!


I'm working on a tool for automated creation of our ISM-Projects. Most of the needed interfaces or access function are available, but some are missing:

  • File type registration
  • Shortcut properties or shell properties for shortcuts
  • Dialog manipulation for the installation UI sequence

(If you found more, please add)


The only way to solve this for me is doing the following:

  1. Creating the project file using the COM automation interface
  2. Doing all the stuff which is supported by the interfcae
  3. Setting the project file format to XML
  4. Saving and closing the project
  5. Opening the project file as a XML document
  6. Adding all missing data to the table definitions
  7. Saving the XML file
  8. Reopening the project via COM
  9. Setting the project file format back to binary
  10. Saving and closing

Does anyone have a better idea for this? What do you think about my solution?




Stefan Krueger

Stefan Krueger


  • Administrators
  • 13,269 posts

Posted 08 June 2013 - 08:03

The binary project file format is using the MSI file format, so you could directly modify the tables using MSI functionality. (If you rename the .ism to .msi you can open it in a MSI editor like Orca or InstEd)


  • Full Members
  • 47 posts

Posted 10 June 2013 - 10:03

Great hint! I remember, I had heared about this in the past, but have forgotten it until now. Thanks! Using the MSI API is much more comfortable indeed!