wix3.7

问题 My project needs to have the ability to install 2 versions or more simultaneously. as far as i can find, the solution i have found is changing the upgrade code for each build of the installer. however i want to do this automatically. in regular GUID i just use "*" but this won't work for upgradecode. is there a way to generate new upgradecode in every wix prebuild or any other solution? <?xml version="1.0" encoding="utf-8"?> <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi" xmlns:util=

问题 Using WIX 3.7, I want to pass a connection string into a custom action. However, since the connection string contains ';' the custom action data is not being parsed correctly. <CustomAction Id="PopulateActionPrep" Property="PopulateAction" Execute="immediate" Value="CONNECTIONSTRING="[CONNECTIONSTRING]";PRODUCTVERSION=[ProductVersion]" /> I tried using quotes to escape the connection string but that did not work. When I read the CONNECTIONSTRING property from CustomActionData it comes back

问题 Recently we discovered that we have a duplicate component GUID in our Wix script. The common GUID is used for 2 files with different names but in the same directory. I did some searching on the net found that, this can lead to problems later on, but cannot find any satisfactory resolutions of the same problem. Is there a safe way of resolving this issue? Thanks. 回答1: Can you rename the files and give them both a new guid each ? This is the safest approach - it decouples all reference count

问题 We are using Wix V3.11 to build an msi setup for our C#-Application. We have a 32 Bit and an 64 Bit build for each version: The preallocated installation path for the 32 Bit build is: 'C:\Program Files (x86)'. The preallocated installation path for the 64 Bit setup is: 'C:\Program Files'. We use the following declaration to set the paths: <?define bitness = $(var.Platform) ?> <?if $(var.Platform) = "x86" ?> <?define ProgramFilesPath = ProgramFilesFolder?> <?define Win64 = no?> <?else?> <

问题 I wrote a Boostrapper UI in C# for Net Framework 2.0 using Win-Forms. It started working fine and designed forms are responding as expected. Here is my Wix Bundle Code: <?define TargetFile=$(var.MyBA.TargetDir)$(var.MyBA.TargetFileName)?> <?define BootstrapConfigFile=$(var.MyBA.ProjectDir)BootstrapperCore.config?> <Bundle Name="Bootstrapper1" Version="1.0.0.0" Manufacturer="Farrukh" UpgradeCode="54c4a4a4-dca8-4ae4-b2f4-5e3f3fd8cb92"> <BootstrapperApplicationRef Id=

问题 I'm asked to upgrade ver 1.0.0.0 to 1.0.0.1. By default, when I tested with a dummy installer, if we change the product code, both 1.0.0.0 and 1.0.0.1 would install side by side. But if we do the ver 1.0.1.0 (while changing product code), it would do the upgrade. Here is my upgrade segment: <Upgrade Id="{354E9DAE-EB70-4BCC-BD93-AC20ACE3F370}"> <UpgradeVersion Maximum="$(var.ver)" Property="DOMAJORUPGRADE" MigrateFeatures="yes" IncludeMinimum="yes"/> </Upgrade> Question: Is there any method to

问题 I have Visual Studio 2008, 2010, and WIX37.msi (WIX 3.7) installed on my machine. However, I am unable to see WIX project type in Visual studio 2008/2010. Do I need to install additional tool/plugin? 回答1: I have Visual Studio 2008 and Visual Studio 2010 installed on my machine and I installed WiX v3.7 RTM from Codeplex. Things work okay for me. There is a known issue in VS2008 that requires you to set an MSBuild property called RunWixToolsOutOfProc to true . This occurred because parts of WiX

问题 Here is my situation: I create a normal WiX Setup project. Then I try to check some prerequisites like if the .NET framework is installed or not. It seems that I am not able to do this from a WiX Setup project. So I create WiX Bootstrapper project and am able to check for and install those prerequisites. I try to use the WiX Bootstrapper in the WiX Setup project but can not. The examples I see was, the WiX Bootstrapper project uses the Setup project with the MsiPackage tag. It seems strange

问题 I have a number of Visual C++ projects in a Visual Studio 2010 solution. Also in this solution is a WiX project that builds the installer for the executable that is the product of one of the C++ projects. The executable has a resource file in its project which writes the version of the program to the executable. Now I'd like to version the WiX-built installer with the same number as the one written to the executable by the resource file. I've searched the WiX related posts on StackOverflow

问题 I am getting an ICE03: String overflow warning for the following code: <CustomAction Id="CustomActionID" Return="check" Property="SomeProperty" Value="VERY LONG STRING COMES HERE" Execute="immediate"/> This code is included in a separate .wxs file in a fragment. If I include this directly within the "Product" tag then the warning disappears. This also happens with the following code: <Binary Id="SomeBinaryWithAVeryLongName" SourceFile="SOURCEFILE" /> I would like to find out why is this