wix3.5

Using pkgmgr to install IIS 7

末鹿安然 提交于 2019-12-08 11:03:40
问题 I am using following custom action to install IIS 7 using .msi if its not already installed on targeted system. I am getting following errror and my installation fails. I have used quite a few CA in my msi and all work well. However for this one I am not able to figure out what the problem could be? Executing this command directly on cmd prompt works perfect. Can anyone provide any suggestions as to what am i doing wrong? Please advice Targeted OS: Windows 7 -32 bit CustomAction Code:

Use WIX to install side by side versions of the same IIS site

喜夏-厌秋 提交于 2019-12-08 01:10:56
问题 Is it possible to use WIX to install side by side versions of the same IIS website. Including the ability to upgrade them individually? I've searched high and low and can't find anything on the internet for this. Also why is using heat to harvest files automatically with each build such a no no? Having to manually update the file structure in WIX when it's already handled in VS and source control is such a pain if you're adding views, models, controllers a lot during development. I'd like to

Why would MST not include files with different content

十年热恋 提交于 2019-12-07 23:55:59
问题 Trying to make a multilingual installer - the process is working in general, but seems to be failing for localised files that are to be installed. Each of the localised installers works fine as a standalone and installs the localised files like the eula.pdf. I'm hoping that I'm just missing a flag on the transform generation step (or maybe using the wrong tool?) Process being to start by having a bunch of installers 1 for each language. To build each installer we are 'lighting' using -b

WiX WebSite creates second duplicate binding when ConfigureIfExists set to yes

不羁的心 提交于 2019-12-07 18:37:13
问题 I have an installer I am modifying where we are modifying a web site in IIS. The requirements state that the end user must create the site first in IIS. We read the site information they choose from a dropdown in the installer for their site, and store the information in properties in WiX. I have a WebSite element under a component, and have the ConfigureIfExists set to yes. A lot of this seems to be working great, it resets the directory of the site to where the website is on the drive. The

Wix Major Upgrade and Install Context Issues

回眸只為那壹抹淺笑 提交于 2019-12-07 17:58:25
问题 I have a Wix project that I have set to allow major upgrades. I'm using WixUI_Advanced for a choice between per-user and per-machine installs. When I install and upgrade per-user everything works as expected, the installer recognizes an upgrade and there is only one entry in Programs and Features. However when I choose a per-machine install, it starts duplicating entries in Programs and Features (even when both install and upgrade are per-machine and to the same folder). Looking at the

How to execute multiple launch conditions on installer exit

孤者浪人 提交于 2019-12-07 07:30:53
问题 I've managed to get WIX to launch my application on exit, but not sure how to schedule two custom actions using the WixShellExecTarget property. One CA is to launch an app and the other is a web page based on a url from another CA. These are both launched if the appropriate checkboxes are checked. <!-- Custom action for executing app --> <Property Id="WixShellExecTarget" Value="[#Application.exe]" /> <CustomAction Id="LaunchApplication" BinaryKey="WixCA" DllEntry="WixShellExec" Impersonate=

Re-cached msi still running old custom action

浪子不回头ぞ 提交于 2019-12-07 05:15:54
问题 I have made a change to a custom action in my msi file to not attempt to stop a windows service if the service is stopped or stop pending. However, after re-caching the msi using msiexec /fv mymsi.msi, when running the major upgrade to the next version (which also has the corrected service stopping custom action) the verbose logging is showing that the old custom action code is still being run even though the cached msi was updated. I even ran a binary comparison of the cached msi against the

WiX unresolved reference to symbol media 1 in section fragment

寵の児 提交于 2019-12-06 20:08:40
问题 I am trying to build my WiX Project in Visual Studio 2010, but everytime I build, I receive the following error messages: Unresolved reference to symbol 'Media1' in section 'Fragment:' Unresolved reference to symbol 'Media1' in section 'Product{67DC7AE3-030F-4A24-AC3F-7AE7D0C32D07}' The project includes one Product.wxs file and one heat-generated wxs someComponents.wxs (my fragment) file. I am referencing components in the heat-generated wxs file in Product.wxs. The sections where I am

Use WIX to install side by side versions of the same IIS site

老子叫甜甜 提交于 2019-12-06 13:15:51
Is it possible to use WIX to install side by side versions of the same IIS website. Including the ability to upgrade them individually? I've searched high and low and can't find anything on the internet for this. Also why is using heat to harvest files automatically with each build such a no no? Having to manually update the file structure in WIX when it's already handled in VS and source control is such a pain if you're adding views, models, controllers a lot during development. I'd like to be able to publish the site during a TFS build and then harvest the output for the installer. Is there

CAQuietExec Command string must begin with quoted application name

假如想象 提交于 2019-12-06 08:47:51
Ok I believe I'm following the online example in Wix3.5 for doing quiet commands yet I cannot seem to get my command to be executed quoted. <Component Id="MapObjectsRuntime' Guid='*'> <File Id = 'Mo23rtEXE' Name='Mo23rt.exe' Source='....' KeyPath="yes"/> <Component> <Property Id = "QtExecCmdLine" Value="Mo23rt.exe" /> // I've tried single & double quotes, and double double quotes around Mo23. <CustomAction Id = "InstallMapObjects" BinaryKey="WixCA" DllEntry="CAQuietExec" Execute="immediate" Return="check" /> <InstallExecuteSequence> <Custom Action="InstallMapObjects" After="InstallFinalize"