The consequence is that it captures files that are not built like .ini files and that the file in question is not equal to the one of the manual installation procedure.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
If I recall WPS7 only add correct formatted .INI files to the INIFile table and the rest to the File table.
Previous versions had some problem capturing incorrect formatted, so these would have to be added manually after the capture.
Answered 12/10/2008 by: AngelD
Red Belt

Please log in to comment
0
It defaults to that behaviour. However, during the process of creating the WSI, you get the option of treating the INI as a file. Choose that and you're set. Following that, you can compile your missive to the vendor, enquiring why their brain-dead developer(s) decided to use the INI extension for files which aren't in INI format.

EDIT:
Oops! We crossed paths! :) Kim, my experience is that WPS is pretty dumb with INIs, in that any text file with an INI extension will be shoe-horned into the INIFile table.

FWIW, even for correctly-formatted INIs, if they're of considerable length, compilation to MSI takes F O R E V E R. In that situation, I convert to installing them as files and, if any dynamic content is required (say, a property needs to be passed to an INI entry), I use my VBScript INI class in a CA.
Answered 12/10/2008 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity