Re: [WiX-users] Tutorial about handling upgrades in Wix 3.7

Thanks everybody! On Wed, Apr 17, 2013 at 11:19 PM, Phil Wilson wrote: > .. And this example describes it: > > http://www.joyofsetup.com/2010/01/16/major-upgrades-now-easier-than-ever/ > > And note that RemoveExistingProducts is early in the sequence, after > InstallValidate, and that results i

[WiX-users] Registering files

Hi Steven, Approaching again for help :-) I have 2 issues regarding registering the installation files in the registry a)The installer has around 400+ components(dll's and ocx's) which has to registered, am using the for all the 400+ files and its getting successfully registered at the specifi

[WiX-users] Why in Preprocessor the "Not Equal To" is "!=" while in conditional string is "<>".

It is not very intuitive. I first write: $(var.MinimumVersion)?> and it says: "error CNDL0162: An illegal number was found in the expression '$(var.CurrentVersion)<>$(var.MinimumVersion)'." -- Precog is a next-generation a

[WiX-users] Why in Preprocessor the "Not Equal To" Operator is "!=" while in conditional string is "<>".

I feel that it is not very intuitive. I first write: $(var.MinimumVersion)?> and it says: "error CNDL0162: An illegal number was found in the expression '$(var.CurrentVersion)<>$(var.MinimumVersion)'." -- Precog is a next-

Re: [WiX-users] Passing parameters to upgrade uninstalls

That is sufficient for my needs (not removing a registry key when upgrading), thanks Rob! On 17 April 2013 23:35, Rob Mensching wrote: > Unfortunately, no. The child MSI just gets `UPGRADINGPRODUCTCODE`. > > > On Wed, Apr 17, 2013 at 12:13 AM, Simon Stevenson > wrote: > > > Is it possible to p

Re: [WiX-users] Tutorial about handling upgrades in Wix 3.7

.. And this example describes it: http://www.joyofsetup.com/2010/01/16/major-upgrades-now-easier-than-ever/ And note that RemoveExistingProducts is early in the sequence, after InstallValidate, and that results in removal of the oler product before installing the new one. I don't know what a FO

Re: [WiX-users] Burn restore after reboot not working

This post may help: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Resume-Installation-Plan-td7579146.html Easiest thing to do is to create a custom object that keep

Re: [WiX-users] Command line args for help

Classification: Public Marco, that is what this forum is for :) Steve -Original Message- From: Marco Tognacci [mailto:mark...@live.it] Sent: April-17-13 3:31 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Command line args for help Thanks for all, s

Re: [WiX-users] Command line args for help

Thanks for all, sorry for my trivial questions. > From: r...@robmensching.com > Date: Wed, 17 Apr 2013 12:22:12 -0700 > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] Command line args for help > > Today you have to write it all yourself. You can see this in wixstdba. > > > On W

Re: [WiX-users] Command line args for help

Today you have to write it all yourself. You can see this in wixstdba. On Wed, Apr 17, 2013 at 12:17 PM, Marco Tognacci wrote: > I have implemented the Help page in Burn setup using WPF custom UI.I'd > like to add all the command line args, is there any way to have the help > text reporting the

Re: [WiX-users] Tutorial about handling upgrades in Wix 3.7

Classification: Public Sounds like a MajorUpgrade... Removes the older version, installs the new version... Steve -Original Message- From: Hans ter Horst [mailto:hoshis...@gmail.com] Sent: April-17-13 3:14 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users]

Re: [WiX-users] Question about /layout option

The former. On Wed, Apr 17, 2013 at 12:13 PM, Marco Tognacci wrote: > I have implemented the /layout option in my Burn setup. the only thing > that it do is to copy all the setup.exe that I have made.I have a single > file setup, with all the resources embedded inside.This option is used only >

[WiX-users] Command line args for help

I have implemented the Help page in Burn setup using WPF custom UI.I'd like to add all the command line args, is there any way to have the help text reporting the usage of the setup base command line args like /install, /uninstall, /help...?I'd like to have the base setup help where to add only

[WiX-users] Tutorial about handling upgrades in Wix 3.7

Is there a tutorial or a reference post available that explains the principles of how to write an installer that first uninstalls an older version before installing the version included in the MSI but that would leave newer versions unaffected unless a FORCE parameter is supplied on the interface?

[WiX-users] Question about /layout option

I have implemented the /layout option in my Burn setup. the only thing that it do is to copy all the setup.exe that I have made.I have a single file setup, with all the resources embedded inside.This option is used only to download all files needed to run the setup if this is web based?Or it cou

[WiX-users] Wix ExePackage can't activate log using Burn

I have an exe setup package that I have to install in the chain of Burn, for this I have added an ExePackage.When the Burn setup is running I have the logs for each msi in the format [WidBundleName_Date]_[MSIPackageName].log, but I have no the log for the exe package, if I run the exe with this

Re: [WiX-users] Burn restore after reboot not working

Yes. You'd need to persist your state yourself. The Plan is only valid for a single Apply and is discarded after. It is never persisted because the machine state could change between the Plan and the Apply. On Wed, Apr 17, 2013 at 11:45 AM, Marco Tognacci wrote: > As I have made the planned act

Re: [WiX-users] Burn restore after reboot not working

As I have made the planned action, after reboot, is there any way (in Burn bootstrapper application) to persist the previous planned info about packages and features?If not I have to add a variable with the PlannedState for each package and feature that I have planned to install, right? > From:

Re: [WiX-users] WiX vs NSIS

Off topic and I know Alain was just joking but I don't want people to start off confused about the company I'm creating. I'm not creating a company to provide consulting services to replace anyone doing installation work. In fact, my goal is to create a company that supports the people doing insta

Re: [WiX-users] WiX vs NSIS

Nick, Shoot me an email and we'll chat about it. I need to explain all the finer points of *WHY* we use MSI and once you fully comprehend the subject it'll be an easy sell. Regards, Chris From: "Nick Miller" Sent: Wednesday, April 17, 2013 8:10 AM

Re: [WiX-users] Burn RunOnce entry is too long...

Yeah, bug. On Wed, Apr 17, 2013 at 8:08 AM, Phil Wilson wrote: > I had the same issue with RunOnce. The solution was to create the RunOnce > data in a file and have the RunOnce key start the program with a command > line that said "hey, the data you want is in this file". > > Phil > > -Orig

Re: [WiX-users] Burn RunOnce entry is too long...

I had the same issue with RunOnce. The solution was to create the RunOnce data in a file and have the RunOnce key start the program with a command line that said "hey, the data you want is in this file". Phil -Original Message- From: rowbot [mailto:jamesnrow...@yahoo.co.uk] Sent: Wedne

Re: [WiX-users] WiX vs NSIS

On 17/04/2013 14:39, Alain Forget wrote: > 3) Finally, throw in the fact that NSIS hasn't been supported since 2009, > while WiX is a very active and supportive open-source community. Even > further, if he wants some time down the line, it would be possible to contact > a consulting company to o

Re: [WiX-users] WiX vs NSIS

Assuming the report about NSIS not using Windows Installer technologies is true, that should be enough to rule it out as far as I am concerned. Known logging details, known tools for removal/upgrading, etc. all make WI useful. Since it is sometimes arcane, that's where the usefulness of WiX come

Re: [WiX-users] WiX vs NSIS

Perhaps all the arguments you need have already been mentioned in this thread? 1) Being technically proficient, perhaps he would understand the inherent costs of maintaining the mass of now NSIS code versus the relative conciseness of WiX (as mentioned by Rob). 2) Follow that up with an example

Re: [WiX-users] Passing parameters to upgrade uninstalls

Unfortunately, no. The child MSI just gets `UPGRADINGPRODUCTCODE`. On Wed, Apr 17, 2013 at 12:13 AM, Simon Stevenson wrote: > Is it possible to pass parameters to the msi being uninstalled during an > upgrade? > > I am using the Upgrade tag to do my upgrades. > > ---

Re: [WiX-users] Web installer - Bootstrapper

Take a look at the current wix38 branch. The WiX Bundle is turned into a single self-extracting executable to be hosted on CodePlex just before final release. Then it goes back to being a web bundle when we host the weekly builds of http://wixtoolset.org/releases On Tue, Apr 16, 2013 at 10:00 PM,

Re: [WiX-users] WiX vs NSIS

Hey guys, thank you for all of your great responses. Allow me to provide a little background, over the past few weeks I have been learning Wix for a special project I worked on. I've gone through the tutorials, I've read the book by Nick Ramirez, and have been able to create a custom managed

[WiX-users] Burn RunOnce entry is too long...

Hi, I've got a bundle which ends up putting a command line in the runonce key (post-reboot) that is longer than 256 characters... the effect being that after reboot, the bundle is not restarted (the command fails sliently) I could shorten the exe name but if the user id in the %temp% path is re

[WiX-users] Passing parameters to upgrade uninstalls

Is it possible to pass parameters to the msi being uninstalled during an upgrade? I am using the Upgrade tag to do my upgrades. -- Precog is a next-generation analytics platform capable of advanced analytics on semi-struct