This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
troycumbo
Level 3
‎Aug 21, 2013 04:21 PM

System Search only works when built from IDE, not command line

I have a Basic MSI project that uses System Search to locate files by searching folders. Locating the files sets properties that are install conditions for the project.

When run from a build generated by the Installshield IDE, System Search locates the files and sets the relevant properties as expected. When run on the same machine, using a build of the same ISM but generated by the command line builder, System Search fails miserably. The path resolves correctly, such that it can be copied from the MSI log and pasted into Windows Explorer, revealing the file that is claimed to not exist.

Is there some idiosyncrasy I must appease in order to get an installer from the command line builder that functions identically to that produced by the IS2012 IDE?
Labels (1)
Labels
0 Kudos
(1) Reply
troycumbo
Level 3
‎Aug 22, 2013 01:09 PM

PEBKAC. NAnt script that inserts version number with build fell victim to Microsoft's peculiar treatment of whitespace in System.Xml.XmlDocument.

If you do such manipulation in your build scripts, be sure your task uses the preserveWhitespace attribute (or your custom task uses that attribute on the document or an XmlWriterSettings descriptor).
0 Kudos