windows-installer

问题 I want to let the user select the language before start the welcome dialog in WiX, so that the installer can install the different features for each language. So far, I have created my own custom dialog that contains ComboBox, I am aware of how to insert custom dialog between any other dialog, but I have no idea how to insert it before the WelcomeDlg. 回答1: I have not done it but I am sure it can be easily done: At the bottom of the WelcomeDlg you should see this: <InstallUISequence> <Show

问题 I have a WiX file where I have to do a version comparison to check prerequisites. The expression looks something like this: <Publish (attributes...)> <![CDATA[(VERSION<"7.0") OR (other expressions)]]> </Publish> This was working fine until now as the major version numbers went 7 to 8 to 9. We are now moving to version 10 and the string comparison is failing as "1" is less than "7". I would like "10.0"<"7.0" to evaluate to false as I intend to compare versions, but the expression evaluates to

问题 This is my .wxs file Particularly I managed to install a service as a LocalSystem user, and started it: <!-- Directory where [prey]/versions/[version] will be --> <Directory Id="ProgramFilesFolder"> <Directory Id="INSTALLLOCATION" Name="Prey"> <Directory Id="VersionsDir" Name="versions"> <Directory Id="VersionDir" Name="$(var.ProductVersion)"> <Directory Id="BinDir" Name="bin"> <Directory Id="BinWindowsDir" Name="windows"> <Component Id="CronServiceExe" Guid="ECC25B2A-FB2E-425A-92AD

问题 This Microsoft tool adds an INVALID Microsoft digital signature when you build an MSI. Anyone know of a simple way to stop the tool from adding the digital signature? Or an easy way to remove digital signature after the build? VS2015 Installer Projects link https://visualstudiogallery.msdn.microsoft.com/f1cc3f3e-c300-40a7-8797-c509fb8933b9 The MSI file works fine even with the bad signature. BUT, when someone tries to download the MSI with the Edge browser, it blocks the download and shows

问题 I have an installer based on the WixUI_Advanced that allows users to choose their install scope (per user or machine wide). When upgrading (have an existing app with a lower version installed) I would like to hide the install scope screen and automatically select the install scope they chose last time. How can I tell what install scope was used for the previous installation? Edit Looking at my MSI logs I can see that my existing installation is found: // Existing user specific installation

问题 As part of my Installshield project, I need to place some files in the user's Roaming app data folder ( C:\Users\<Username>\AppData\Roaming\MyApp\MyFile ). For this I've created a component, and set its destination to [AppDataFolder]MyApp . While this works fine when I run as an Administrator, when I run the installer as a standard user (elevating the privileges during installation using the admin's account/password), MyFile gets copied to the Administrator's roaming folder ( C:\Users\

问题 Currently I'm trying to move the WixUIBannerBmp, WixUIDialogBmp and WixUILicenseRtf WixVariables and their corresponding binary files to a wixlib. Unfortunately when building it ignores these and uses the defaults. My Library.wxs: <Fragment> <WixVariable Id="WixUILicenseRtf" Value="licence.rtf" /> <WixVariable Id="WixUIBannerBmp" Value="binaries/bannrbmp.bmp" /> <WixVariable Id="WixUIDialogBmp" Value="binaries/dlgbmp.bmp" /> </Fragment> where the rtf and bmp files are included in the wixlib

问题 I've inherited an installer with a fairly long history. In a few versions, component GUIDs were not tracked properly, resulting in different component GUIDs for a given file. v1.0: C:\Program Files\Foo\Foo.exe {GUID_A} v2.0: C:\Program Files\Foo\Foo.exe {GUID_B} v3.0: C:\Program Files\Foo\Foo.exe {GUID_B} This obviously violates component rules, and requires early sequencing of RemoveExistingProducts to avoid absent files after an upgrade. Each new version installs as a Major Upgrade. It is

问题 Let's suppose I've just created an app in visual studio and now I want to distribute it. I've set the app to release mode and I have a copy of the app that works just fine. My main question is how would I go about creating an installer for it and making sure Windows knows it's trustworthy? Do I have to create some sort of certificate? I've been searching and downloaded NSIS but I'm not sure how to use it so I just used Inno Setup Compiler which works just fine. Sometimes Avast checks my

问题 When trying to install a software on a terminal server, we get the following error. Any help is appreciated. msi install log shows the following error: MSI (s) (1C:04) [07:27:28:750]: Executing op: ActionStart(Name=InstallODBC,Description=Installing ODBC components,) Action 7:27:28: InstallODBC. Installing ODBC components MSI (s) (1C:04) [07:27:28:750]: Executing op: ODBCInstallDriver(DriverKey=Microsoft FoxPro VFP Driver (*.dbf),Component={612B3EFA-F178-4C50-A049-B99BE6DCACE0},Folder=C: