windows-installer

问题 I'm facing a weird problem and I can't find a working solution. Thanks in advance for any help. I developed a Windows Service in C# that use Newtonsoft.JSON library to parse the result from a bunch of WebAPI. The service is deployed with MSI and everything was working perfectly. The first version of the service was using Newtonsoft.JSON 6.0.8, but recently I moved to version 11.0.2. I packed a new MSI (with correct version/Product Id/Upgrade Id to ensure upgrading) and I'm trying to deploy

问题 I created a WIX Burn setup. The Bundle chained multiple .MSI files for global installation (all MSI support downgrading). <Bundle Name="APP 4.3.0" Version="4.3.0" Manufacturer="Manu" UpgradeCode="$(var.UpgradeCode)"> <Chain> <PackageGroupRef Id="VCppRedistPackage"/> <PackageGroupRef Id="DotNet4Package"/> <MsiPackage Id="CrystalReportPackage" SourceFile="$(var.SolutionDir)_CommonFiles\CRRuntime_32bit_13_0_9.msi" DownloadUrl="http://MyAppRuntime/CrystalReport_NET40/CRRuntime_32bit_13_0_9.msi"

问题 I'm trying to use iExpress to install dependencies on a small script that I've created on NodeJS. The iExpress package simply installs the packages Node: msiexec /i node.msi Then runs a Post installation Batch to put the Javascript into a folder in the %UserProfile% folder. The Post installation Batch is run with: cmd /c post_install.bat In the batch there is a line which isn't working: npm install <dependency> This doesn't seem to work immediately after the MSI install, but it will work the

问题 I've got a WiX deferred custom action that conditionally modifies some registry keys. For the changes to take effect, a reboot is required. I'd like the user to get the standard dialog box that prompts them to reboot after the installation completes. How can I schedule a reboot from a deferred custom action? 回答1: Why do you have a custom action doing something that MSI/WiX knows how to do natively? A cleaner approach would be to have registry values associated with a component that has the

问题 I've got a WiX deferred custom action that conditionally modifies some registry keys. For the changes to take effect, a reboot is required. I'd like the user to get the standard dialog box that prompts them to reboot after the installation completes. How can I schedule a reboot from a deferred custom action? 回答1: Why do you have a custom action doing something that MSI/WiX knows how to do natively? A cleaner approach would be to have registry values associated with a component that has the

问题 I simply want to do an installer that will move some files into Program Files, set up a start menu link, and appear in the add/remove program to be uninstalled. For the time being I'm happy to punt on the start-menu link as that seems relatively straight forward The caveat is that I specifically want this to be build-able from a script without any sort of global installs. That means no Visual Studio extension nor any global installation of the WiX toolkit. I was able to find WiX on nuget

问题 After the user goes through the Setup Wizard, and makes a few choices, the usual thing is to display the VerifyReadyDlg to say "Are you ready to install?" The built-in VerifyReadyDlg is static. It does not present a summary of the choices he made previously. I'd like to modify it so that it does. How can I do that? Example "Static" text: Intelligent text: I don't believe I can modify the Control table in the MSI, because mods during the installation process are not allowed. I found

问题 Is there some easy, hassle-free way to get the MSI installation to always replace the .exe file (i.e. Primary Output) whenever the .exe file is more recent? This is just basic and common sense. Wherever I search there are always complicated discussions about major and minor versions and patches. There must be some simple way to ensure the file gets replaced during an install. Otherwise, what is the MSI file actually doing during the whole installation procedure. It's like a fake install where

问题 I can find plenty of info on how msi upgrades. E.g. info about minor upgrade, small upgrade, major upgade, and their use case and limitations. However, I cannot find info on the upgrade behavior of merge module, such as: It seems like msm does not have any way to specify minor, small, or major upgrade. So which way it behaves in? Does it uninstall old version first or only update changed files? Is there any way to specify from which version it can be upgraded like msi? Can I add/remove/rename

问题 I can find plenty of info on how msi upgrades. E.g. info about minor upgrade, small upgrade, major upgade, and their use case and limitations. However, I cannot find info on the upgrade behavior of merge module, such as: It seems like msm does not have any way to specify minor, small, or major upgrade. So which way it behaves in? Does it uninstall old version first or only update changed files? Is there any way to specify from which version it can be upgraded like msi? Can I add/remove/rename