installer

问题 We've gotten a custom action that runs command-line to work as such: <CustomAction Id="OurAction" FileKey="OurInstalledExe.exe" ExeCommand="our command line args" Execute="deferred" Return="check" /> The problem is, the user sees a console popup when the command runs. The command line requires UAC elevation, but should not require any user interaction. We also install the file with the setup, the custom action runs After="InstallFiles". How do we prevent the user from seeing the console? 回答1:

问题 We install an application (MSI) using MSIEXEC with the following command line option: MsiExec.exe /x{code} /qn /liwearucmopvx+ C:\Log\UnInstall.tra MsiExec.exe /iC:\Source\App.msi /qn TARGETDIR=C:\Install ALLUSERS=1 /liwearucmopvx+ %C:\Log\Install.tra Most of the time this works, but sometimes the uninstall fails (not sure why yet, looking into the error). Anyways when this happens I get the following error during the re-install: Another version of this product is already installed.

问题 We use wix to create setups for our application. For the case where the user has already installed an older version of our application, we do a major upgrade with the MajorUpgrade XML element. This is all working as desired: if an older version is installed, it is upgraded transparently. If a newer version is present, the installer aborts with a clear message. However, I now want to change the InstallScope from "perUser" to "perMachine". Unfortunately this breaks the upgrade logic. The new

问题 We are having a System.BadImageFormatException in our MSI installers. I have already read about the target frameworks, but we already checked and it's targeting the correct framework ( .NET Framework 4.5 same with our QA machines). We have exactly the same source codes, but the results of the msi installer compiled by our 'build team' fails, but the msi installer compiled by us 'dev' works. Question is, does the environment where an application was built and compiled affects the output

问题 We are having a System.BadImageFormatException in our MSI installers. I have already read about the target frameworks, but we already checked and it's targeting the correct framework ( .NET Framework 4.5 same with our QA machines). We have exactly the same source codes, but the results of the msi installer compiled by our 'build team' fails, but the msi installer compiled by us 'dev' works. Question is, does the environment where an application was built and compiled affects the output

问题 We're currently using a GUID to identify the application when running our uninstall script which contains msiexec. The problem I'm having is the GUID changes every time I install the latest version of the application, so I was wondering if there is a different way that I can identify our application running using msiexec? 回答1: The usual way that people get around the various ProductCode values in this situation is to start with the more constant UpgradeCode. Given the UpgradeCode, you can use

问题 I'm using Windows XP SP2, and installed Ruby through Ruby 1.9 one click installer. Then when I try to using ri, I get the following response, can anyone help me with my problem? C:\Documents and Settings\eyang>ruby --version ruby 1.9.1p243 (2009-07-16 revision 24175) [i386-mingw32] C:\Documents and Settings\eyang>ri --version ri 2.2.2 C:\Documents and Settings\eyang>ri String Updating class cache with 0 classes... Nothing known about String C:\Documents and Settings\eyang>ri Updating class

问题 I am trying to write a .bat for the first time. I am trying to install .msi using script, currently we are installing manually by double clicking on it. Path from : d:/installed sw/$folder/.msi Path to : D:/program files/app/ $folder means, it is different every time, as we are getting new msi to install which are provided in folder created by current date. Here is the script I am trying: @echo off Title HOST: Installing Updates on %computername% echo %computername% set server=\\SERVERNAME or

问题 Some software (for ex. the NetBeans IDE) ship the Linux installers in .sh files. Curious about how exactly they 'package' a whole IDE into a 'shell script', I opened the file in an editor. I saw some plain text shell scripting code and then some random gibberish, which I reckon is 'binary' or non-plain text. I am wondering how they mix plain shell scripts and then probably call the 'non-readable' stuff, which would be the binaries. Any insight on this? 回答1: Basically, it's a shell script

问题 Which library or macro that deletes only installed files when the uninstallation is run would you recommend? I'm aware this kind question has been asked alot but I'm looking for advice on the most current and easiest to use macro/library. As in the past,I used old macros that were posted on NSIS Website for things like Command Line Argument parsing and had problems with the code and implementation. My understanding is that there are 2 so far(are there more?): Advanced_Uninstall_Log Uninstall