windows-installer

问题 How can I tag or modify a .msi binary with custom information? How can I give website users individual downloads, so that they don't have to sign in again in the app? Some websites offer personal/customized/tagged installer downloads. When you run the file, the executeable already knows who you are and automatically signs you in. Examples are: join.me where passing the presenter role, triggers a download for the other party and automatically connects them into the right conference spotify had

问题 I have Basic MSI project (I use InstallShield 2013 Professional). Suppose it has ProductName DefaultProductName . I can build it and get setup.exe. It will appear in a list of Installed Programs in Control Panel with DefaultProductName name if I install it. Now, suppose that I want to change my ProductName from DefaultProductName to NewProductName during install, in runtime (to be more clear: I'm talking not about Upgrades, but about situation when I'm installing my product on "clean" box).

问题 I am authoring a very small patch to a very large package, it's sole purpose is to update a single file and add four smaller ones. Using the WiX help as a guide I am able to generate the MSP file. However, a patch runs apparently it runs the original package in reinstall mode, with all the custom actions and whatnot that go along with it, which is not what I want. Further research turned up the OptimizeCA property of the MsiPatchMetadata table, and its WiX equivalent OptimizeCustomActions

问题 I tried msiexec /i "yarn-1.10.1.msi" TARGETDIR="C:\programs" /qb It installed but not in TARGETDIR, did I miss something ? 回答1: You can try the following command line instead: msiexec.exe /i "yarn-1.10.1.msi" INSTALLDIR="C:\programs" /qb Standards Compliance : Installing underneath %ProgramFiles% is always recommended. Creativity in deployment is generally always overrated and usually causes unnecessary problems. However, you could have an SOE setup that requires custom paths? Path Update : A

问题 This is a follow-up on this question, which was solved by locating the installation package on a local drive. Unfortunately, it seems that on some machines, this doesn't solve it. I have the following log available === Verbose logging started: 03.07.2013 23:17:03 Build type: SHIP UNICODE 4.05.6001.00 Calling process: C:\WINDOWS\system32\msiexec.exe === Resetting cached policy values Machine policy value 'Debug' is 0 ******* RunEngine: ******* Product: C:\myInstallation.msi ******* Action: ***

问题 We have a setup in which we have a service that we try to install and run. For some reason, the service cannot start(due to a port already in use). This isn't critical for us and should not stop the setup. The service is declared like this: <DirectoryRef Id="BIN"> <Component Id="MyService" Guid="*" SharedDllRefCount="yes"> <File Id="MyService.exe" Name="MyService.exe" KeyPath="yes" Vital="no" Compressed="default" DiskId="1" Source="$(var.DirDotfuscated)\MyService.exe" /> <ServiceControl Id=

问题 I'm trying to build an NSIS installer and package it with necessary drivers (MSI files from the vendor). Eventually, I'd like to install these drivers silently in the backgroud. However, I cannot seem to get it working properly. In my NSIS script, I have the following: ExecWait 'msiexec /i "$INSTDIR\Flash.msi INSTALLDIR="$INSTDIR\Drivers\Flash""' It seems to execute; if I remove the INSTALLDIR switch from the above snippet, it'll run the driver installation as expected. But when I leave it in

问题 I have a bootstrapper (C# windows forms applications) that trigger two different msi files consecutively out of its resource. The instance transforms between the msi are 'paired' such that one instance transform from the first msi shares an UpgradeCode with one instance tranform from the second msi; these are the pairs that are installed together via the bootstrapper. The 'core' msi (the first msi that runs) includes the MajorUpgrade element such that when a higher-versioned 'core' msi is run

问题 I am using the WiX toolset to build an installer, I want to read the version from a text file. The text file is located in mybootstrapper like below: below is the code where i want to read the content of text file <Bundle IconSourceFile='product.ico' Name="Retail Grip" Version="Version.txt" <!-- i know this is not correct --> Manufacturer="Company Name" UpgradeCode="PUT-GUID-HERE"> 回答1: Oh, it is a WiX bundle - and that's " Wax "? I hear it is a WiX tool of sorts? I am not sure exactly how it

问题 Currently I'm distributing a software product that includes three merge modules: Microsoft_VC80_CRT_x86.msm ATL.msm policy_8_0_Microsoft_VC80_ATL_x86.msm Some customers use packaging technology that doesn't like these MSM files (I think because they have technical problems with them writing to WinSxS). Can I just distribute the dll files directly into my application's Program Files folder, and if so which dlls do I need? Is it just atl80.dll? 回答1: Your alternative is to run the VC_redist.exe