windows-installer

问题 I have a command line I want to run during the install of a merge module (created by WiX) with the below code. <CustomAction Id='SetWebsiteProtocols' Execute='commit' Return='ignore' Impersonate="yes" FileKey='Web.config' ExeCommand='c:\windows\system32\inetsrv\appcmd.exe set app "Default Web Site/My Website" /enabledProtocols:http,net.tcp,net.pipe' /> <InstallExecuteSequence> <Custom Action="SetWebsiteProtocols" After="InstallFiles"/> </InstallExecuteSequence> When I run the command on the

问题 in a wix burn bootstrapper bundle : how to detect whether ms vcredist 2013 x86 is present or not? i'm doing a check for the Upgrade Id / UpgradeCode of that particular package, but the bundle always installs it afresh, even though it is installed already. ... <Bundle> ... <Chain> <!-- redist packages --> <PackageGroupRef Id="redist"/> ... </Chain> </Bundle> <Fragment> <PackageGroup Id="redist"> <PackageGroupRef Id="redist_vc120" /> ... </PackageGroup> </Fragment> <Fragment> <!-- vcredist 2013

问题 This question is asking whether one of the ICE57 validators creates a false positive error report. I am using WIX 3.9 to generate an installer. I want a per machine installation with non advertised shortcuts. This WXS example installs a text file and a shortcut to open the text file: <?xml version="1.0" encoding="UTF-8"?> <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi"> <Product Id="*" Name="ShortcutTest" Language="1033" Version="1.0.0.0" Manufacturer="Widget Co" UpgradeCode="--YOUR

问题 I'm looking at using Burn as a bootstrapper for an installer and I need to pass in a couple of arguments into the MSI. I know that the way to do this is to use MsiProperty elements, the issue I am having is with displaying the UI to capture those properties. I'm aware that I can create a completely custom UI via the managed bootstrapper application host, however this is turning out to be a lot of work to implement for a relatively minor tweak to the bootstrapper. I've found this blog article

问题 Closed . This question is opinion-based. It is not currently accepting answers. Want to improve this question? Update the question so it can be answered with facts and citations by editing this post. Closed 5 years ago . I have been evaluating the wide range of installation and web deployment solutions available for Windows applications. I will just clarify here (without too much detail, these tools have been covered in other questions) my understanding of the options: NSIS - Free tool that

问题 So I have this setup project in Wix and wanted to have a shortcut on the desktop. This must be easy you might think. But that is not the case. All the code snippets found on the Internet did not work. After a few hours of struggling and reading the documentation I finally got it right, so I am sharing it with you here. 回答1: The shortcut is a non-advertised one, hope this helps someone. Remember to put the component in your feature tag. <Directory Id="TARGETDIR" Name="SourceDir"> <Directory Id

问题 I have been asked to only deploy files that are bundled into MSI package. MSI contains 4 files, For that I'm using this command: `msiexec /a [path to MSI] TARGETDIR =[Application folder path]` Problem with above command is that it also deploys .MSI file to specified TARGETDIR which i don't want. Is there any workaround/way that i can only deploy that 4 files? 回答1: Not to my knowledge, no. This is an administrative installation, and it is essentially just an extraction of the files embedded in

问题 I have an existing MSI package which I want to repackage to add installation options (so far the MSI has been installed through the command line with msiexec parameters in a .bat file). Are there, as of today, freeware tools available to repackage the MSI? I was stumbling over WiX but as per my understanding I need VisualStudio to complete what I wanted (I dont have VisualStudio)? Thank you! 回答1: What exactly do you want to add to the MSI package? You could use Orca to modify any table in the

问题 Note: This question is also posted on the WiX Users mailing list. I am trying to silently execute a PowerShell script from a WiX produced MSI. However, anytime I run the installer PowerShell hangs. Interestingly enough, according to the installer logs the PowerShell script appears to run successfully. Additionally, if I kill the PowerShell process via Task Manager, the installer cancels the installation and rolls back any changes. PowerShell Script Contents # @param website The website under

问题 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: