Re: [WiX-users] Choose language dialog

You can use themutil extension to author the bundle UI. You can author the UI to end after the user presses Install, at which time the MSI's internal UI would show. However themutil lacks a combo-box which is probably required to allo

Re: [WiX-users] Replace files added in minor upgrade

Some of the things that matter are the command line you use to install the patch, and the value of REINSTALL, whether you added the file to an existing feature or added a new feature (and is that in the REINSTALL list?), and whether you deleted a component, Even changing the primary key of a file o

Re: [WiX-users] After add reference WixNetFxExtension.dll to Setup Project, build failed‏

Hi Sean Thank you for your reply, that's working. > Date: Sat, 14 Mar 2015 13:13:40 -0500 > From: r.sean.h...@gmail.com > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] After add reference WixNetFxExtension.dll to > Setup Project, build failed‏ > > You'll also have to

[WiX-users] Choose language dialog

Hi, I have made my MSI and embedded multiple languages into the setup process. Not it works by property TRANSFORMS=":1049" to select ru-RU language. As I would now like to have a custom language selection dialog, I have moved to the bootstrapper project, which uses a variable to be inserted into

Re: [WiX-users] Replace certain changed files in a major upgrade

That's probably because you have sequenced the major upgade "late" which results in file replacement rules being followed. Try sequencing after InstallInitialize to get a full uninstall of the older product followed by the the install of the new one. --- Phil Wilson On Mon, Mar 16, 2

[WiX-users] Burn MsiPackage DisplayName property does not localized

Hello, I want to know how to localized DisplayName Property in Burn MsiPackage. I tried but not success. Thanks in advance. Mrugesh Patel -- Dive into the World of Parallel Programming The Go Parallel W

Re: [WiX-users] heat fragments go one directory too low

-srd Suppress harvesting the root directory as an element. http://wixtoolset.org/documentation/manual/v3/overview/heat.html -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/heat-fragments-go-one-directory-too-low-tp7599560p7599571.html Sent fro

Re: [WiX-users] Namespace prefix 'netfx' is not defined.

Is the case of a typo? Is WixNetFxExtension.dll listed as a Project Reference? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Namespace-prefix-netfx-is-not-defined-tp7599569p7599570.html Sent from the wix-users mailing list archive at Nabble.com

[WiX-users] Namespace prefix 'netfx' is not defined.

Hi, I am authoring WiX project in VS 2010 using Votive. And added reference to WixNetFxExtension.dll . Also in my product.wxs file added xmlns:netfx attribute: http://schemas.microsoft.com/wix/2006/wi"; xmlns:netfx="http://schemas.microsoft.com/wix/NetFxExtension";> All components and

Re: [WiX-users] heat fragments go one directory too low

Thanks for this hint. Turns out that -srd is command-line position dependent. I had appended it to the end of the command line, where it didn't seem to do anything, but moving it in front of the -out made it work. Eric -Original Message- From: Nir Bar [mailto:nir@panel-sw.com] Sent

Re: [WiX-users] (WiX) Write product info to registry for dual purpose installer

I found the problem. MSIINSTALLPERUSER="" is not enough. Only when I set ALLUSERS="1" it's written to HKLM. I expected the dual purpose installer checking the MSIINSTALLPERUSER property and not the ALLUSERS one. -Original Message- From: Egger, Jerome [mailto:jerome.eg...@uster.com] Sent

[WiX-users] Replace certain changed files in a major upgrade

?Hi, When I do a major upgrade I want to replace also changed files. The customer sometimes changes the resource files. Then it won't be upgraded by Major Upgrade anymore. How can I force this? Thanks! Robin Lutteke Disclaimer Dit bericht met eventuele bijlagen is vertrouwelijk en uitslui