Re: [WiX-users] resource strings issue with wix 2.0

Thank for your replay , At present situation its difficult to migrate to Wix 3.x, In this scenario updating WixUI_en-us.wxl is the standard practice ? Thanks Naufal -Original Message- From: Bob Arnson [mailto:b...@joyofsetup.com] Sent: Tuesday, September 28, 2010 10:03 PM To:

Re: [WiX-users] resource strings issue with wix 2.0

I just took a quick glance at the wix 2.0 code. You can supply more than one WXL file to light.exe. You just can't duplicate any strings AND the CodePage must match. Go ahead and put your custom strings in a new file. You just can't override any strings already in the WixUI_en-us.wxl without

[WiX-users] wix source on codeplex is behind of sourceforge weekly

Hi, I'm doing some patch stuff right now and I saw the patch related changes on sourceforge wix35.feed from Sep 25th. I then updated my cloned source from codeplex and discovered that the latest commit was done on Sep 10th here. So where are the last two weeks gone? Another point I want to

Re: [WiX-users] Continuing questions about WiX

Hi, 1) the first warning could be ignored safely. This only means that ProgramFile is defined twice, once in your file and in crystal reports msm. (This is common for most MSMs) The other errors are from an old crystal msm. There was a similar thread in Februar. See

Re: [WiX-users] Advantage of using Patch Creation Properties over plain WiX?

I recently worked with both and failed to get the Pyro method to work to my liking. WiX was excluding obviously changed files in some of my early builds and I couldn't find definitive information on how it determines which files to include in the patch cab. Later I also discovered that it was

Re: [WiX-users] Continuing questions about WiX

There is a feature in the works in WiX v3.6 to address #2. That feature is right behind finishing the huge features of Burn. I hope everything gets unlocked in next two weeks and bugs start getting fixed (instead of feature work). On Thu, Sep 30, 2010 at 6:34 AM, Nick Davey n...@idocket.com

[WiX-users] how to get error code returned by custom action

Hi, Does anybody have any idea, how to get the error code returned by a custom action? I want to display a dialog box based upon the return code of the custom action. Regards, Sanjay Rao -- Start uncovering the many

[WiX-users] Macro Installer from multiple individual products, simplest implementation ?

Hi, I'm new to this forum and it seem, I din't post to the correct subforum, so sorry and here's my second try. I have built several Wix product installers for which each of them is an independent product and has its dedicated msi installer file and also a wix merge module associated to it. I

Re: [WiX-users] how to get error code returned by custom action

Windows Installer has no such concept of return codes when calling custom actions.   To get the behavior you are looking for will depend on what kind of custom action you are using.   Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good

[WiX-users] Automatic remove of older version

Hi, I made an installer with WIX 3.5 that deploy things for a BI Solution. When I have a new version of my WIX Installer, and the client run the installer (MSI), can it automatically uninstall any older version installed on the PC and start the installation of the new version ? It is something

[WiX-users] Uninstall question

Our product requires another product to be pre-installed. We then overwrite some of the other products files during our install as the integration points between our two products. If they are in Folder A and my product goes into Folder B, then it would be true that when we detect them we are

[WiX-users] providing differing output names for 32-64 bit packages

Hi: I have a visual 2010 solution which amongst other things has an installer being compiled for 32/64 bit. I don't appear given that I have two different platforms configured to be able to provide differing output names for these different platforms. I could do this with a post build

Re: [WiX-users] providing differing output names for 32-64 bit packages

I use 2 project files located in the same directory. Each one of them targets one platform, builds only one configuration and includes the same source files. Lena -Original Message- From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk] Sent: Thursday, September 30, 2010 5:09 PM To:

[WiX-users] wix preprocessor and votive

Hi: Is there a defined variable within the wix pre-processor that allows me to detect the currently active platform I'm compiling for in visual studio. I have a project with both win32, and x64 platforms, and I want to #ifdef code based on the platform in my wix source. Cheers Sean.

Re: [WiX-users] Uninstall question

The only way that kind of sharing will ever really work is if you use the same component guids. If you are replacing a file from Product A and not using the same component guid as A you've broken the rules, after which things get unpredictable. Permanent=yes is typically not a good solution,

[WiX-users] Question with Browse dialog box behaviour with invalid folders

I notice a strange behavior with browse dialog box and I'm wondering if there is any way around the issue. I have the following WiX script to setup the dialog box: Dialog Id=BrowseTargetDlg Width=370 Height=270 Title=!(loc.BrowseDlg_Title) Control Id=PathEdit

Re: [WiX-users] Automatic remove of older version

Richard Here's some help on doing upgrades http://blogs.technet.com/b/alexshev/archive/2008/02/15/from-msi-to-wix-part-8-major-upgrade.aspx Looking at your code, I think you may have sequenced RemoveExistingProducts in the wrong place. It either needs to be InstallExecuteSequence

[WiX-users] My Install Finished ExitDialog box get shown almost off screen on Windows 7 if my Progress Dialog is minimized

I got this bug report from QA and I'm not quite sure how to fix. It seems to happen only on Windows 7. I have an ExitDialog box that get shown on successful install like so: UI Dialog Id=ExitDialog Width=370 Height=270 Title=!(loc.ExitDialog_Title) ...

Re: [WiX-users] wix preprocessor and votive

This might work: ?if $(sys.BUILDARCH) = x64 ? ... ?else? ... ?endif? CONFIDENTIALITY The information contained in this message is confidential. It is intended to be read only by the individual or entity to whom it is addressed or by an authorized designee. If the reader of this message

Re: [WiX-users] wix preprocessor and votive

The .wixproj file defines the Platform property that should be getting passed automatically to candle. You should be able to use something like this: ?if $(var.Platform) = 'value' ? ... ?else? ... ?endif? Where 'value' is one of the platforms defined for your project. Edwin G. Castro Software

Re: [WiX-users] providing differing output names for 32-64 bit packages

I update the .wixproj file to use a different OutputName for each platform. In my case, I simply append the value of the Platform property: OutputNameMyProductName$(Platform)/OutputName Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax:

[WiX-users] Overwrite files with higher version on major upgrade

We need to overwrite files with higher version on major upgrade: SomeFile.dll (3.0.1.1) - SomeFile.dll (2.1.0.0) How do we do it? -- Start uncovering the many advantages of virtual appliances and start using them to