Blair wrote:
> BTW, unless your condition is in the "MainExecutable" component you may want
> to try not putting any children in your PatchFamily element. If PatchFamily
> is empty it checks everything for inclusion. Otherwise it filters to only
> include what is in that list.
>
Having originall
Blair wrote:
> First, what was your commandline to pyro? You have to match the @Id of your
> PatchBaseline element to the wixmst you supply from torch in your pyro
> commandline (e.g. "-t Sample sample.wixmst"). Also your commandline to torch
> should include "-p".
>
> Also, between your baseline a
First, what was your commandline to pyro? You have to match the @Id of your
PatchBaseline element to the wixmst you supply from torch in your pyro
commandline (e.g. "-t Sample sample.wixmst"). Also your commandline to torch
should include "-p".
Also, between your baseline and your upgraded you sho
Blair wrote
>
> If you have a lot of customers you will probably be better off
> distributing
> an MSP file which can be run right from your web site instead of requiring
> a
> special command-line like a minor upgrade MSI will.
Cheers, this seems the best solution as it has been distributed a b
: Tuesday, October 13, 2009 2:36 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Installer screw up
I have also had a similar experience with a third party MSI, which we fixed
by editing the cached copy.
The other option you could try is writing a Minor Upgrade for
] Installer screw up
We had something like this but managed to catch it after it had gone to only
one customer. The
installer we gave them had a condition that prevented it from being
uninstalled. I had to install
it locally and find the cached copy. You can either do this by searching the
We had something like this but managed to catch it after it had gone to only
one customer. The
installer we gave them had a condition that prevented it from being
uninstalled. I had to install
it locally and find the cached copy. You can either do this by searching the
Windows folder or
lo
Hi, I've a bit of a problem.. I've created an installer previously which worked
fine but required a certain version of IE to be installed which a while ago
worked fine. Foolishly I didn't specify the IE version properly and also didn't
stop the checks during uninstall. Now MS has kindly pushed t
8 matches
Mail list logo
