MSI doesn't read INI file when deployed silently
Hey guys,
I have a Vendor MSI file I'm trying to get deployed, I've customized it with a transform and it's mostly working fine. The program itself uses an INI file to hold connection information etc. If you have an INI file in the MSI folder when installed, it will use the contents of this file as the INI file in the destination folder.
If I install manually with the GUI it reads the INI file no problems. If I install silently however, it doesn't read the INI at all!
(Hope its clear what I mean!)
Any ideas before I just script it?
Answers (1)
The Windows Installer engine does not use INI files natively so my guess is that there is a Custom Action (CA) in the MSI which is reading it and acting upon its content. Since this is not happening when the MSI is instaled silently, it's probable that the vendor has perpetrated the "rookie MSI Packager" error of not having a copy of the CA in the ExecuteImmediate phase. So, to rectify, simply copy the CA from the UserInterface phase to the ExecuteImmediate phase.
Comments:
-
Gah, your right! Just waiting on the tests to finish now but looks like that's it. Just moved back into a gov't job and having to deal with all these small specialised software vendors again is driving me mad! - mhouston100 10 years ago
-
Once you're done, the next job is the tongue-in-cheek email to the vendor, enquiring whether they'd be interested in purchasing a package which works when installed silently :-) - anonymous_9363 10 years ago
