wix3.6

WiX - Set Installdirectory dynamically over CustomAction [C#]

不想你离开。 提交于 2019-12-06 07:45:09
I'm about to create an installer, now i have to set the install-directory depending on the operation-system. My directory-tree: <Property Id="TARGETDIR" Value="C:\" /> <Directory Id="TARGETDIR" Name="SourceDir"> <Directory Id="TARGETDIRECTORY" Name="MyApplication"> <Directory Id="CONFIG" Name="Config"> <Directory Id="FOLDER2" Name="Folder2" /> </Directory> </Directory> </Directory> if i set the TARGETDIRECTORY in the c#-custom-action, the targetdirectory gets set correct, but the CONFIG/FOLDER2 just have the old links. How can i force them to adjust them to the new paths? because they are

How do I get WiX to generate a 64-bit MSI?

你离开我真会死。 提交于 2019-12-06 06:04:31
I am using WiX 3.6 and VS2010. I have a 32-bit installation working and I'm trying to get a 64-bit installation working. I set the Platform to "x64" in the Configuration Properties. I set the Platform attribute in the Package tag to "x64" in the install script. I changed the installation directory from "ProgramFilesFolder" to "ProgramFiles64Folder". I added the attribute Win64="yes" to each component. I thought this was enough to generate a 64-bit MSI, but it still insists on installing everything in "Program Files (x86)" instead of "Program Files". What am I missing? My mistake. It was

Bootstrapping sequence validation issue using WiX 3.6 and Burn

ぐ巨炮叔叔 提交于 2019-12-06 05:00:21
<?xml version="1.0" encoding="UTF-8"?> <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi" xmlns:util="http://schemas.microsoft.com/wix/UtilExtension"> <Bundle Name="My Test Program" Version="1.0.0.0" Manufacturer="Microsoft" UpgradeCode="cc7cfeae-c3a4-4430-841e-f927de3f9f95"> <BootstrapperApplicationRef Id="WixStandardBootstrapperApplication.RtfLicense" /> <util:RegistrySearch Id="FindDotNet35SP1InstallRegValue" Root="HKLM" Key="SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5" Value="SP" Variable="DotNetFramework35SP1InstallRegValue" /> <util:RegistrySearch Id=

WIX | Remove *.config file on install

时光怂恿深爱的人放手 提交于 2019-12-06 03:53:14
I have multiple config files (for different environments). During install user get to select the environment, and based on that correct files are copied. I want to delete the extra files that are not used. I am using but it doesn't seem to be working. I don't get any errors as such, in the log I see action getting executed but files are not deleted. Can anyone please point what I am doing wrong? <Component Id="RemoveFiles" Guid="C5D634C2-744E-4CA5-BB44-F3DE88482AB5"> <RemoveFile Id="RemoveConfigs" Name="???_*.config" On="install" /> </Component> My RemoveFile table also looks like FileKey

How do I add a reference to a VSTO project to a WiX Installer project in Visual Studio 2010?

梦想的初衷 提交于 2019-12-06 01:44:41
问题 I've got a Visual Studio 2010 solution which contains a VSTO Add-In project. I've also added a WiX Setup project to the solution, and I now need to add a reference to VSTO project in the Setup project, but am unable to do so. When I right click the References in the WiX Setup project, then select Add Reference, then Select the Projects tab the VSTO project doesn't appear in the list of available projects to reference. 回答1: I had the same problem, then I tried to "do it wrong": I added the

How to add custom action to wix setup project

ⅰ亾dé卋堺 提交于 2019-12-06 01:38:48
问题 I have 2 projects in my soliution: 1). Custom action class (CustomAction) 2). Wix setup project (TestSetup) There is CustomAction.cs in CustomAction project: using System; using System.Collections.Generic; using System.IO; using System.Linq; using System.Text; using Microsoft.Deployment.WindowsInstaller; namespace CustomAction { public class CustomActions { [CustomAction] public static ActionResult CustomAction1(Session session) { File.Create(@"c:\installed.txt"); return ActionResult.Success;

How to use MajorUpgrade and RemoveFeatures to remove only specific features and still un-install the previous version of the product

天大地大妈咪最大 提交于 2019-12-05 12:26:50
I swapped to Wix 3.6 from the Microsoft Installer that was packaged with VS 2010. I am trying to release a seamless upgrade to our users by using the <MajorUpgrade/> Tag, however I have one feature that I do not want to be un-installed while performing this major upgrade. As seen below I have RemoveFeatures="[ProductFeature]" which will result in only the ProductFeature being removed and the DataFeature will remain, but this results in the entry not being removed from the "Programs and Features" list in Windows as it is when this parameter is not specified. How can I upgrade properly without

WiX - commit more than one Property to deferred Custom Action

≡放荡痞女 提交于 2019-12-05 03:38:20
I have a problem with my WiX installer in contact with deferred / immediate custom actions. Please excuse my english. I want to surrender some properties, entered by the user, to a deferred custom action. I know that I need a immediate custom action and "CustomActionData" to do that. I´ve implement it at this way. The binary: <Binary Id='myAction' SourceFile='.\TemplateGeneration.CA.dll'/> The immediate custom action: <CustomAction Id='Datenuebergabe' Property='DoSomething' Value='InstalllocVar=[INSTALLLOCATION]'/> The deferred custom action: <CustomAction Id='TemplateGenerationInstallKey'

patching using purely WIX

孤街醉人 提交于 2019-12-05 02:53:25
问题 I am struggling with creating a patch purely using WIX and I was hoping if someone could guide me in the right direction. I have a few hundred source files and I run heat against them to create a harvest file followed by creating a package using candle and light. I need to change a few configuration files and I create a 2nd package with the changes. Using Torch and pyro I create the .wixmst file and then when trying to create the msp file, pyro complains with the following error. pyro.exe :

creating language selection dialog using WiX

怎甘沉沦 提交于 2019-12-05 02:14:32
问题 I have a created a multilanguage installer using WiX. I am running the installer from command line using command "msiexec /i myinstaller.msi TRANSFORMS=":1041" and it is working fine. Now I have created a language selection dialog using bootstrapper. How can I pass the selected language to my WiX installer to launch as per selected language? I got this idea from following links: Can we localize WIX msi and bundle using language selection UI at runtime? http://wix.tramontana.co.hu/tutorial