[WiX-users] Subscribe Edit to SelectionChanged event of ListBox

Hello all, I'm facing the problem while trying to make a dialog for choosing start menu folder for creating application shortcut. There are 2 controls on the dialog: Edit for entering new folder name (if user chooses to create a new folder for shortcut) and ListBox in which existing folders are

[WiX-users] Setup upgrade needs to care for 4th part of version number

Hello All, due to political issues (see below) my setups need to be able to upgrade when only the 4th part of the version info changes. Example: V1.0.0.1 needs to upgrade V1.0.0.0. My installers always do major upgrades, the product GUI always changes (that is OK and not an issue to discuss).

Re: [WiX-users] Setup upgrade needs to care for 4th part of version number

I had a similar problem the way I got round it was to set the upgrade code to include the maximum version, e.g. UpgradeVersion/@IncludeMaximum=yes. This will generate an ICE61 which you will need to ignore. This isn't perfect as 1.2.3.4 will be downgraded by 1.2.3.3 but if you are sure two

Re: [WiX-users] Setup upgrade needs to care for 4th part of version number

Hello Neil, thank you - I didn't find this one. It is not perfect, but sufficiently good :-). If someone can tell me the perfect solution, I'm still open to it. Thanks again! Dirk On Mon, Jul 13, 2009 at 12:00, Neil Sleightholm n...@x2systems.com wrote: I had a similar problem the way I got

Re: [WiX-users] Query: Difference between WiX and Visual Studio Setup Build

hi Vijay, please go thru the following link as it will give u very basic info about wix with separate from other setup creation tools available in market. http://blogs.newsgator.com/inbox/2007/06/why_wix.html if you are not doin anything in the UI sequence... that means u dont need to modify

Re: [WiX-users] Setup upgrade needs to care for 4th part of version number

The perfect solution would be for Windows Installer to understand 4 part version numbers like every other system on the planet :-) One other point, I schedule RemoveExistingProducts after InstallValidate, it gets a bit more messy if this is not the case. Neil Neil Sleightholm X2 Systems

Re: [WiX-users] Setup upgrade needs to care for 4th part of versionnumber

Another perfect solution would be to control the Product Version attribute yourself. Could you put the political version number into the Product/@Name attribute ? That way the bosses would see the number they want in add/remove programs and you can use Product/@Version as MSI intended.

[WiX-users] Modular installation

Hello, This probably isn't a Wix-specific question, but please excuse me for asking here - I'm after a Wix-based solution. I have to make the installer for a product that is sold on a module-by-module basis. The number of the modules is not known beforehand. A module ships on its own disk, which

Re: [WiX-users] Setup upgrade needs to care for 4th part of versionnumber

Hi, Hello All, due to political issues (see below) my setups need to be able to upgrade when only the 4th part of the version info changes. Example: V1.0.0.1 needs to upgrade V1.0.0.0. My installers always do major upgrades, the product GUI always changes (that is OK and not an issue to

Re: [WiX-users] Hiding passwords in the installation log file

Doh! Thanks a lot Bob! Regards, Rob -Original Message- Date: Sun, 12 Jul 2009 22:49:34 -0400 From: Bob Arnson b...@joyofsetup.com Subject: Re: [WiX-users] Hiding passwords in the installation log file To: General discussion for Windows Installer XML toolset.

[WiX-users] Updating web.config field value depending on if machine's 64bit or 32bit

Hi, I have a field in web.config that needs environment variable of %ProgramFiles% or %ProgramFiles(x86)% depending on if the machine installing is 64 bit or 32 bit. Is there a way to substitute the values during install time by detecting this and setting the appropriate values? Thanks so

Re: [WiX-users] Updating web.config field value depending on if machine's 64bit or 32bit

XmlFile is your friend. -Original Message- From: Erica Chang (PROJECT) [mailto:eri...@microsoft.com] Sent: Monday, July 13, 2009 1:59 PM To: 'wix-users@lists.sourceforge.net' Subject: [WiX-users] Updating web.config field value depending on if machine's 64bit or 32bit Hi, I have a

Re: [WiX-users] Updating web.config field value depending on if machine's 64bit or 32bit

Windows Installer automatically handles translating the ProgramFilesFolder property for 32-bit vs. 64-bit platforms. Are you using an XMLFile element to set the web.config value? Use the [ProgramFilesFolder] property within the XMLFile element, and you should get what you want. - Don Benson -

Re: [WiX-users] Updating web.config field value depending on if machine's 64bit or 32bit

Keep in mind it's better to avoid XmlFile / XmlConfig and just rely on standard IIS custom action functionality, if possible. I don't know enough about your particular scenario to know if it's possible in this case, but if you can throw a [ProgramFilesFolder] into your IIS authoring somewhere

Re: [WiX-users] Updating web.config field value depending on if machine's 64bit or 32bit

To the best of my knowledge As long as your installer is tagged correctly as a 32bit installer by setting the Platform attribute of the Package node to x86 like this: Package Id=* InstallerVersion=200 Compressed=yes Languages=1033 Platform=x86 InstallPrivileges=elevated

Re: [WiX-users] Updating web.config field value depending on if machine's 64bit or 32bit

[ProgramFilesFolder] will be automatically set to the appropriate folder. Windows Installer takes care of this property automatically. On Mon, Jul 13, 2009 at 3:51 PM, Erica Chang (PROJECT) eri...@microsoft.com wrote: What we are doing is installing sample sites that needs the location of the

Re: [WiX-users] Updating web.config field value depending on if machine's 64bit or 32bit

Yes, that make sense for me. But to use xmlFile I have to link to wixca.wixlib, how do I do that? Also when I tried to add Platform node to Package Id I got: The Package element contains an unexpected attribute 'Platform' Thanks lots. Erica -Original Message- From: Phil Sayers

[WiX-users] 32-bit app launching 64-bit MSI problem

I have a simple 64-bit MSI that I made install 1 64-bit dll to System64 folder. Under the following circumstances, MSI gets an error: 1. That file already exists in the real C:\Windows\System32 folder 2. The install is launched through a 32-bit app (not explorer.exe). Anything that can launch

Re: [WiX-users] Setup upgrade needs to care for 4th part of versionnumber

We also ran into this problem. It is just stupid that visual studio projects use 4 part version numbers and MSI only supports 3. Visual Studio doesn't. We're talking in the context of major upgrades and the ProductVersion property. In Visual Studio that's the Version property of the Setup

Re: [WiX-users] 32-bit app launching 64-bit MSI problem

Depending on how your 32-bit app calls the install, it's possible that it's using the 32-bit copy of msiexec.exe, which means that the System32 folder gets redirected by default, which could mean that the file doesn't actually exist. You may be able to use something like ProcessExplorer to verify

Re: [WiX-users] 32-bit app launching 64-bit MSI problem

Are you actually launching msiexec.exe? The one in the SysWow64 folder rather than the 64-bit one? Phil Wilson -Original Message- From: Michael Ballou [mailto:mbal...@eeye.com] Sent: Monday, July 13, 2009 2:47 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] 32-bit app

Re: [WiX-users] 32-bit app launching 64-bit MSI problem

No. My customer is using a 3rd party shell type application (Total Commander) that happens to be 32-bit to run the setup. When launching the MSI from there, it gets the error. The MSI log shows the calling process is Msiexec.exe in the SysWow64 folder, so it is the 32-bit one. This also happens

[WiX-users] 64bit package compiling

I have x64 Windows XP. I tried to make 64 bit package by setting attribute: Package Id=* Platform=x64 / and during compilation got an error: light.exe : error LGHT0310 : Failed to open package for validation. The most common cause of this error is validating an x64 package on an x86 system.