The fragmentation will allow you to limit what changes in your newer build
are actually contained in the patch, but the application of the patch is
always performed via a repair of features.
Blair
-Original Message-
From: Sanjay Poria [mailto:sanjay.po...@xanalys.com]
Sent: Tuesday, Febr
Hi.
I have the following code:
(ADDLOCAL="Feature_Default")
(REMOVE="ALL")
However, the FileKey above is defined in a nested Directory Element as seen
below:
Are you running a 32 bit installer on a 64-bit machine? If so, then
"%SystemRoot%\system32" is going to resolve to "C:\Windows\SysWOW64". So,
make sure that "C:\Windows\SysWOW64\Novell\Nici" exists or the search will
fail.
--
View this message in context:
http://windows-installer-xml-wix-toolset.
Hi,
I tried making the change you suggested, however it does not really work.
>From the log file, I see the following message:
>'%SystemRoot%\system32\Novell\Nici' is unavailable. However the directory
>does exist.
Thanks,
Carl
>>> jhennessey 2/6/2012 6:17 PM >>>
Try setting the Regi
http://www.bredeau.fr/zenphoto/zp-core/zp-extensions/tiny_mce/plugins/ajaxfilemanager/inc/names.php?ryan164.jpeg";>http://www.bredeau.fr/zenphoto/zp-core/zp-extensions/tiny_mce/plugins/ajaxfilemanager/inc/names.php?ryan164.jpeg
It could be a services dependency - you'd see that in the services applet.
Make sure that there isn't something in the ServiceControl table even if it's
just spaces that might not show. I've noticed that spaces can affect this kind
of thing. It might literally be trying to stop a service that's
I have an installer that stops three services, but get an error:
MSI (s) (90:44) [12:11:17:558]: Executing op:
ActionStart(Name=StopServices,Description=Stopping
services,Template=Service: [1])
Action 12:11:17: StopServices. Stopping services
MSI (s) (90:44) [12:11:17:558]: Executing op:
ProgressT
I got this working by adding my image file to the payload -
& in the .thm file:
Also, in case anyone is scratching their head like i was with localisation,
you need to define two WixVariables:
Otherwise it will use the default ones.
--
View this message in contex
I have a question about how burn handles packages that install to different
locations.
I have these 3 packages:
msi package A
msi package B
msi package C
I want to create two installers with burn using these three msi packages
My first burn installer installs:
msi package A to location 1
msi pack
I set some of my unversioned files as CompanionFile's to versioned binaries.
That way, if the versioned binary changes version, the CompanionFiles are
replaced too. That changes the installer behavior. Then I author my
PatchFamily to include the files I want in the patch.
Usually, my un-vers
I'm exploring Burn and would like to try using my own theme with
WixStandardBootstrapperApplication.Foundation. I'm probably being dense but I
haven't managed to get anything working so far and the documentation isn't
exactly extensive (yet).
A few quick pointers as to how to get started would b
Hi again,
I solved the problem by creating the same directory structure used to
create the initial installer. The files can then be found by pyro and
the patch is created as expected.
Regards, Michel
Am 06.02.2012 20:17, schrieb Michael Scheepers:
> Hi there,
>
> I have a problem when I try t
John,
I'm not expert on but
I created a different fragment for each component/file in my original
distribution (a rather tedious process) so that only those files I specify in
my patch specification are included. You may want to try that and see if it
fixes your issue. As far as I know, a
That's correct.
http://blogs.msdn.com/b/heaths/archive/2011/04/02/10131862.aspx
See the section "A single change will reinstall the entire parent feature"
-Original Message-
From: john.burak [mailto:john.bu...@telvent.com]
Sent: 07 February 2012 00:15
To: wix-users@lists.sourceforge.net
Is there a way to tune msp patch, so that all non-versioned filles (or
all files, if possible), this patch contains, would 100% overwrite files
on disk while patching?
01.02.2012 20:46, Blair wrote:
> With the very same base MSI view installed with the very same options, and
> the very same pat
15 matches
Mail list logo