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?
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?