Re: [WiX-users] Redist an external MSI

2011-06-23 Thread Sameer Arora
Appreciate your for pointers Pally. Let me start by looking at dotnetinstaller. Thank you, Sameer On Wed, Jun 22, 2011 at 2:52 AM, Pally Sandher pally.sand...@iesve.comwrote: To redistribute 3rd party installation packages you will need to use a bootstrapper. WiX v3.6 has Burn in development

[WiX-users] Issue with MajorUpdate Element

2011-06-23 Thread CoolBreeze
As I understand from the Wix docs that when the MajorUpdate element is used with the attribute AllowSameVersionUpgrades=no that I should be able to run my installer a second time and the new installation would be treated by MSI as a new product independent from the previous one. I'm not finding

Re: [WiX-users] Custom UI Controls

2011-06-23 Thread ColinBowern
@Palbinder - I am looking specifically how to inject custom controls - not change the order of the UI or modify the dialog layout itself. Any of the search results I had found before posting referred to custom layout rather than custom controls. After some further research it looks like the SQL

Re: [WiX-users] Issue with MajorUpdate Element

2011-06-23 Thread Brian Rogers
From the sound of it you would actually have to do some custom work around the modify scenario. You don't want to install the actual bits more than once, correct? Sent from my Windows Phone From: CoolBreeze Sent: Thursday, June 23, 2011 6:55 AM To: General discussion for Windows Installer XML

Re: [WiX-users] Issue with MajorUpdate Element

2011-06-23 Thread Castro, Edwin G. (Hillsboro)
As I understand from the Wix docs that when the MajorUpdate element is used with the attribute AllowSameVersionUpgrades=no that I should be able to run my installer a second time and the new installation would be treated by MSI as a new product independent from the previous one. I'm not

Re: [WiX-users] Issue with MajorUpdate Element

2011-06-23 Thread CoolBreeze
Edwin as you described this is the behavior that is occurring as the ProductCode is different, but the ProductVersion and UpgradeCode are the same. Are my only options to accomplish what I want to: 1. Create a new MSI with a different ProductCode and UpgradeCode for each Brand. 2. Configure my

Re: [WiX-users] Issue with MajorUpdate Element

2011-06-23 Thread David Watson
Yes you are probably correct depending on exactly how you are supporting multiple brands. If you want 2 identical products but the installation branded with different logos and installed to a different location, your best bet is to make multiple msis (you can do this from a shared codebase to

[WiX-users] Wix project error in TFS build

2011-06-23 Thread ansariwn
Hi, I am building a solution that contains a Wix v3.6 project on Team Foundation Server (TFS 2010). The solution also contains some other class library projects. The TFS build is unsuccessful with the following error: light.exe : error LGHT0103: The system cannot find the file

Re: [WiX-users] Issue with MajorUpdate Element

2011-06-23 Thread CoolBreeze
Thanks, our ideal result is to give the installer to our production support team, who will run the single msi however many times is needed and each time specify a different brand (virtual directory). This is sounding like the instance transforms is what will be needed; otherwise, there is the

Re: [WiX-users] Issue with MajorUpdate Element

2011-06-23 Thread Castro, Edwin G. (Hillsboro)
Read up on instance transforms first... If I remember correctly, you need to know ahead of time how many instance transforms you are going to support. That requirement sort of makes instance transforms useless in my opinion. On the other hand, perhaps you can use regular transforms to change

Re: [WiX-users] Wix project error in TFS build

2011-06-23 Thread Castro, Edwin G. (Hillsboro)
I'm noticing something similar in some my builds. What do you mean by manually set the dependency? Edwin G. Castro Software Developer - Staff Digital Channels Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail

Re: [WiX-users] Issue with MajorUpdate Element

2011-06-23 Thread CoolBreeze
Thanks for the info. I think the easiest route is going to be to create multiple msi's as needed. This way there won't be any jumping through hoops and there shouldn't be any concerns when it comes to upgrading the installation of a particular brand's website files. On Thu, Jun 23, 2011 at 1:02

Re: [WiX-users] Show Installer Log file

2011-06-23 Thread Wilson, Phil
There's still an error dialog shown isn't there? Can't you use the same approach? Phil Wilson -Original Message- From: lokanath devineni [mailto:ldevin...@yahoo.com] Sent: Wednesday, June 22, 2011 8:38 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Show Installer Log

Re: [WiX-users] Wix project error in TFS build

2011-06-23 Thread John Bergman
If you are using the MSBUILD capabilities on your build servers, update the command line in the build to provide a verbose output, you should be able to see what the problem in the log. We noticed that in 2010 that sometimes there are dependency issues, and if that is the case (ie, the missing

Re: [WiX-users] Issue with MajorUpdate Element

2011-06-23 Thread John Cooper
You can generate the instances in a preprocessor for loop. Since this stuff is branded, you're likely to know a countable list of brands. You could define list in a semicolon delimited var, pass it to a ?foreach? and build your transforms that way. Not perfect, but doable. -- John

[WiX-users] How to set custom output folder for MSI wix project

2011-06-23 Thread Zong Yang
Hi, Does anyone know how to set a custom output folder for a MSI wix project? I have a pretty standard wix MSI project, it outputs to en-us,fr-fr, de-de folder automatically, however in order to be consistent with other projects, I would like to output the msi file to en, fr, de folder. Of