![]() They would need to be passed to such a script, perhaps as command line argument(s). Script executed by calling CSCRIPT.EXe has no such restrictions but, conversely, can't natively "see" MSI properties. Hopefully, it follows that you can't then use things like WScript.Echo and WScript.Sleep in such CAs. While this is not: Set objWshShell = WScript.CreateObject("Wscript.Shell") ![]() To illustrate, this is valid in an embedded CA: Set objWshShell = CreateObject("Wscript.Shell") Confusingly, you *will* be able to create WScript objects, e.g. However, there are situations where the developer of an installation package finds it necessary. Standard actions are sufficient to execute an installation in most cases. For a list of these actions, see the Standard Actions Reference. Therefore, you won't be able to use the 'WScript' directive (e.g. The Windows Installer provides many built-in actions for performing the installation process. Two, remember that for embedded CAs, the script will be using Windows Installer's interpreter (let's call it that) and not Windows Scripting Host. ![]() Setup.exe can accept command-line parameters that allow you to perform administrative installations, run silent installations, and complete other administrative tasks fill kroger survey form. One, add the 'force' argument to the DeleteFolder method. InstallShield uses setup.exe as the bootstrap loader to call the Microsoft Windows Installer service. That will allow you to access MSI properties (hint: the 'Session' object) in order to get the folder name, thus avoiding any problem with 32-bit/64-bit folder names. Aaaaaaaaaaaaaaaaaaaah! Now it all comes out! :-) The RemoveFile table won't help you here, then, so it's back to script!
0 Comments
Leave a Reply. |