Patchwiz
-
Nir Bar
Freelance Developer
Mail: nir@panel-sw.com
Web: www.panel-sw.com
- C++ On Windows, Linux and Embedded Platforms
- WiX & InstallShield
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patching-a-product-without
Patchwiz or Pure WiX style?
From: Nir Bar [nir@panel-sw.com]
Sent: June 28, 2015 6:34 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Patching a product without ProductVersion property
We have a legacy product that was distributed without
We have a legacy product that was distributed without ProductVersion authored
into the MSI.
I don't know how this was done, since ProductVersion is a required property;
however I can only fix that in future major-upgrade releases.
The problem now is that we want to deliver a patch package for this
Hi All,
I'm having some success with creating patches using the melt.exe approach.
However, I have a stumbling block with custom actions and merge modules, as
outlined here:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Creating-Wix-Pure-patch-with-Melt-exe-and-Pyro-exe-fails-td
nuing
Development
Jack Henry & Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
|jocoo...@jackhenry.com
-Original Message-
From: vcur...@hotmail.com [mailto:vcur...@hotmail.com]
Sent: Thursday, January 22, 2015 1:42 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Pat
The component is a service install\remove. We have not set a KeyPath so I
guess Wix is choosing one, but looking at the component table in InstEd the
KeyPath is null for this component.
The machine (A) that is actioning the component I have found has been
through a few product upgrades whereas
sers@lists.sourceforge.net
Subject: [WiX-users] Patching and null KeyPath
Hello.
I'm having an issue with a patch behaving differently on two machine with the
same target installation.
On one machine (A) the component is action-ed during the patch install and on
the other (B) it is not.
Other c
Hello.
I'm having an issue with a patch behaving differently on two machine with
the same target installation.
On one machine (A) the component is action-ed during the patch install and
on the other (B) it is not.
Other components are behaving the same way, I notice that these all have
null Ke
That worked great. For future reference of folks who are perusing the
archives, the SP1 RelatedBundle points back to the original bundle's upgrade
code, and has a new guid as its upgrade code.
I also learned that problems result if the SP1 bundle is built with 3.9 (the
original bundle is built wi
You want the OptionalUpdateRegistration element:
http://wixtoolset.org/documentation/manual/v3/xsd/wix/optionalupdateregistration.html
_
Short replies here. Complete answers over there: http://www.firegiant.com/
Hi all -- things have gone well with our product and Wix 3.8. We are using
the stdba and now I'm working on service pack 1, using torch/pyro/etc. via a
.msp file.
When I create a bundle to install the .msp, a new entry is put into the ARP.
Let's say the original bundle is called "My App". The n
Great! I'll go with option one then. Thanks!
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patching-msi-tp7597706p7597756.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Thanks!
That part I got though. I think you misunderstood my question a bit. The
question was on how to generate patch 1.0.2. Should I generate that so that
it contains the difference between:
1.0.0 ->1.0.1 or
1.0.0 -> 1.0.2
--
View this message in context:
http://windows-installer-xml-wix-t
Hi
I have a MyProduct_1.0.0.msi that I'm going to release and I am planning for
the patchwork that will come. When doing patch 1.0.1 I'll create a patch
comparing the two versions. So far so good...
But the patch 1.0.2. Should that be made comparing againts 1.0.0 or 1.0.1?
Thanks?
--
View thi
Hi All,
I have 2 msi of the same product(on with version 2.0.0.0 and other with
version 2.0.2)
Both msi have the same ProductID,UpgradeID
I have created 2 small patch (msp) on version 2.0.0.0 to upgrade to 2.0.2
Now i want to create a small patch with version 2.0.3 which should work
on both the
Hello,
I'm just new to WiX and maybe, my question don't make sense, this might be
because I'm not an English native speaker.
So here my question:
I'll like to patch / hotfix an application that was installed by an
Bootstrapper Application.
One more question, is it enough to simply increment th
We've decided to go with the approach you've suggested, and I will look into
delta patches to reduce the patch size (although since most of our changed
files will be videos, I would guess deltas wouldn't help much).
As far as each patch superseding the last, is this something we need to
specify in
m: dtkob...@gmail.com
> To: WiX-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Patching compressed VS uncompressed image?
>
> My patches are whole file patches.
>
> There is no UI either in the patches either.
>
> I'll have to check out the hash table and see
My patches are whole file patches.
There is no UI either in the patches either.
I'll have to check out the hash table and see what files may mismatch. It
never mentions anything about the file it's trying to access, it just keeps
mentioning the product it looking for. About every 45 seconds the
Are your patches delta or whole file?
> Date: Wed, 8 Jan 2014 10:46:06 -0800
> From: phildgwil...@gmail.com
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Patching compressed VS uncompressed image?
>
> It could be useful to examine the log where the pat
It could be useful to examine the log where the patching accesses the
network MSI to see what actually happens. Typical reasons include installed
files that no longer match the cached MSI. For example the cached (MSI plus
patches) has entries in the file table that say the version of the file on
di
Can someone tell me why patching a uncompressed image requires the attempt
to look for source? I am not prompted asking for credentials, but the
patch log shows it keeps looking for the original install location like
this:
Resolving source.
MSI (s) (9C:30) [08:23:26:466]: User policy value 'Searc
ailto:phildgwil...@gmail.com]
Sent: Monday, January 06, 2014 3:46 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Patching strategy
If you create whole file patches then you might get that size issue, but
patches can be smaller, the delta between the files.
I don't know
If you create whole file patches then you might get that size issue, but
patches can be smaller, the delta between the files.
I don't know if Burn can do that, but the question is: how does the
customer know when to run it? It's not too difficult for the app to call a
company web service passing
This sounds like a good way to start at least. My one concern is what
happens when the accumulated patches start to get large enough to make size
a concern? Lets say the original data is 2GB, and every month we need to
release a patch that changes 5% of it. After 5 months we're up to a 500MB
acc
The simplest strategy for maintenance per MSI is to build a single
accumulating patch that includes and supersedes previous patches. You build
an updated MSI to create the patch, and the patch is therefore the changes
between the original shipped MSI and the new MSI. Then you have a max
of three pa
I am implementing a new installer for a product that needs to include several
GB of data. I'm planning on having a single MSI for the application, several
MSIs for the data, and using burn to chain everything together.
The data will change periodically and updates will be delivered online, so
pat
ourceforge.net
> Subject: [WiX-users] Patching with Burn - What makes my feature become
> advertise?
>
> Hi,
> I am implementing removable patches with Burn
>
> Such that if I Install RTM, HF1, HF2 then both HFs should be visible
>
> And when I uninstall HF2 ,th
Hi,
I am implementing removable patches with Burn
Such that if I Install RTM, HF1, HF2 then both HFs should be visible
And when I uninstall HF2 ,the machine will return to the state where RTM,
HF1 was installed.
All my HF are cumulative and I build the HF against RTM only,
Meaning HF2 will ta
Wilson [phildgwil...@gmail.com]
Sent: Wednesday, October 23, 2013 8:51 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Patching with BURN-how a patch knows about original
install folder?
...because of my previous comment. Windows Installer knows where every
component's
Phil Wilson [phildgwil...@gmail.com]
> Sent: Wednesday, October 23, 2013 7:04 PM
> To: General discussion about the WiX toolset.
> Subject: Re: [WiX-users] Patching with BURN-how a patch knows about
> original install folder?
>
> Use the WiX "remember property" pattern if
23, 2013 7:04 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Patching with BURN-how a patch knows about original
install folder?
Use the WiX "remember property" pattern if you want to preserve the value
of INSTALLFOLDER from the original install.
Phil Wilso
uesday, October 22, 2013 7:15 PM
> To: General discussion about the WiX toolset.
> Subject: Re: [WiX-users] Patching with BURN-how a patch knows about
> original install folder?
>
> A patch that is an update to installed components doesn't need to know
> folder locations unless
, October 22, 2013 7:15 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Patching with BURN-how a patch knows about original
install folder?
A patch that is an update to installed components doesn't need to know
folder locations unless you need to specify them for some
A patch that is an update to installed components doesn't need to know
folder locations unless you need to specify them for some other reason. For
an update of component C-Guid of product code P-Guid it can locate the path
to any component (as can any program) by calling MsiGetComponentPath
(P-Guid
I wonder when running a patch bundle how the patch bundle (acatually the
MSP) knows what is the install folder used by the RTM?
Looks like we are missing this values in the MSP and many of the
registration we do use a directory defined
in wix msp project
Thanks in advance
--
View this mes
There are ways but Major Version Patches are officially discouraged (see MSDN).
> Date: Sun, 23 Jun 2013 21:41:45 -0700
> From: nickra...@hotmail.com
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Patching multiple versions
>
> Actually, trying my idea didn
Actually, trying my idea didn't work for me. It may not be possible to have a
single patch file that updates multiple versions. However, you may be able
to create a patch for each version that you want to update. For each one,
keep the PatchFamily's Id the same (that way they'll maintain their corr
I haven't tried it, but could you add a PatchFamily for each version that you
want patch? Each PatchFamily would have a Version to identify the product
version to update. You would not use the PatchFamily's ProductCode attribute
at all. Instead, the parent Patch element's TargetProductName would ma
Hello All,
We have a product for which versions 1.0.0, 1.0.1 and 1.0.2 have been
released. For each of these versions, the product code was auto-generated to
enable automatic removal of previous version before installation of new MSI.
Now, we have released version 1.0.3 and I am trying to cr
Thanks for the explanation.
-Original Message-
From: Blair Murri [mailto:os...@live.com]
Sent: Monday, June 17, 2013 1:52 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Patching error
George,
On initial installations Windows Installer seems to
ously used ones (although passwords and
the remember pattern don't work well together).
Hope this helps.
Blair Murri
> From: r...@robmensching.com
> Date: Fri, 14 Jun 2013 21:25:30 -0700
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Patching error
>
&g
; -Original Message-
> From: Phil Wilson [mailto:phil.wil...@mvps.org]
> Sent: Friday, June 14, 2013 3:25 PM
> To: 'General discussion for Windows Installer XML toolset.'
> Subject: Re: [WiX-users] Patching error
>
> It's the "ignoring" part that is the
in patching, but not in
normal install?
-Original Message-
From: Phil Wilson [mailto:phil.wil...@mvps.org]
Sent: Friday, June 14, 2013 3:25 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Patching error
It's the "ignoring" part
p/aa371571(v=vs.85).as
px
So they need to be secure or they are gone when your code runs on the server
side.
Phil
-Original Message-
From: George Fleming [mailto:gef...@microsoft.com]
Sent: Friday, June 14, 2013 1:17 PM
To: General discussion for Windows Installer XML toolset.
Sub
rom: David Watson [mailto:dwat...@sdl.com]
Sent: Friday, June 14, 2013 10:00 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Patching error
If you install your program on a test machine then run a repair from ARP or the
command line does it fail with th
XML toolset.
Subject: Re: [WiX-users] Patching error
What do you mean by "repairs correctly"? The patch log shows errors, so I
assumed that means it didn't repair correctly?
I don't store the values of SERVICEACCOUNT or SERVICEPASSWORD, but they are
provided via command-line
the log
these lines:
Ignoring disallowed property SERVICEACCOUNT
Ignoring disallowed property SERVICEPASSWORD
-Original Message-
From: David Watson [mailto:dwat...@sdl.com]
Sent: Friday, June 14, 2013 1:50 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Pat
-users@lists.sourceforge.net
Subject: [WiX-users] Patching error
I following online instructions and created a patch (msp file). There were
no errors during the creation. When I tried to verify the patch by applying
it, I got following error:
MSI (s) (C0:F0) [13:36:29:463]: Executing op
I following online instructions and created a patch (msp file). There were no
errors during the creation. When I tried to verify the patch by applying it, I
got following error:
MSI (s) (C0:F0) [13:36:29:463]: Executing op: ActionStart(Name=CreateUser,,)
MSI (s) (C0:F0) [13:36:29:463]: Executi
Hi,
I'm having issues trying to get a patch built with WiX (using the Patch
Creation Properties method) to apply to an MSI (also built with WiX) that has
been multi instance transformed. I've logged my efforts to get it working on
StackOverflow:
http://stackoverflow.com/questions/14814014/msi-
Message-
From: Muzikayise Flynn Buthelezi [mailto:muzkay...@gmail.com]
Sent: 05 October 2012 10:26
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] patching issue: adding new file works but this throws
out old files Sequence numbers in msi
Good Morning Team, trust
Hi Peter,
Thanks for your reply..
I've given msi builds which were not designed by me and after Pyro's
complaint, I investigated that in every build, same named components got new
Component ID (GUID).
Although, I've informed the owners and asked them if they are changing the
Component IDs for eac
: wix-users@lists.sourceforge.net
Subject: [WiX-users] Patching Components with different GUIDs?
Hi Guys,
Is that possible to Patch a Component whose GUID was changed in Updated
build?
Pyro gives an error:
I know if I change the GUID in my updated msi back to the one which was in
Original msi
Hi Guys,
Is that possible to Patch a Component whose GUID was changed in Updated
build?
Pyro gives an error:
I know if I change the GUID in my updated msi back to the one which was in
Original msi. But I have a case in which a great number of GUIDs (might be
in thousands) have to be updated then
On 11-Jun-12 14:20, Vishnu wrote:
> Install log shows registry is updated from previous (cached) msi values. I
> applied patch using ORCA tool, and didnt find any new registry changes in
> the patch file (msp). Do we need to create a component for each registry
> values and reference it in Componen
Install log shows registry is updated from previous (cached) msi values. I
applied patch using ORCA tool, and didnt find any new registry changes in
the patch file (msp). Do we need to create a component for each registry
values and reference it in ComponentRef section in PatchFamily element?
--
V
On 07-Jun-12 15:21, Vishnu wrote:
> How to include registry changes in patching ?
They are, if the registry changes are reflected in the upgrade MSI and
the component that contains them is being installed. See a verbose
patch-install log to see what MSI is doing with each component.
--
sig://bo
We have legacy VB6 & COM components dll in our installer. Some of the them
are modified, so we are creating patches to update dlls in client machine.
Based on WIX patching (using Pyro), I created a patch & applied
successfully. All the modified components are getting replaced but registry
changes a
With someone's help, I figured out the approach.
After CostFinalize action, before InstallValidate action, add a customer
action, say UpdateFeatureChange, which changes the feature's reqire state
accordingly.
In DTF, it is as simple as
FeatureInfo featureA2= this.Session.Features["FeatureA2"];
fea
Echo on the question.
I have exactly the same problem:
In my product V1.0, I have
FeatureCommon (always be installed)
Common.dll
FeatureA (optional)
A1.dll
FeatureB (optional)
B1.dll
In my product V1.1 I added A2.dll to feature A
ation)?
Thanks
sanjay
> -Original Message-
> From: Sanjay Poria [mailto:sanjay.po...@xanalys.com]
> Sent: 05 February 2012 21:21
> To: 'General discussion for Windows Installer XML toolset.'
> Subject: [WiX-users] Patching and Pyro Warning PYRO1110
>
> I have cr
I have created an MSI product installer for a product that has a main feature
(call it MF) and a sub feature (call it SF). It is mandatory to install the
main feature but the sub feature is optional.
I am experimenting with creating patches (small updates) using Wix 3.5 for this
product. I hav
cliffe [mailto:pshirtcli...@sdl.com]
> Sent: 12 January 2012 10:20
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Patching
>
> 1. There are a couple of ways that might work for you. It depends if
> you have
> to stick with your current
a version resource that specifies the file version but
it'll will handle unversioned binaries too.
-Original Message-
From: Sanjay Poria [mailto:sanjay.po...@xanalys.com]
Sent: 11 January 2012 23:09
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-us
Shirtcliffe [mailto:pshirtcli...@sdl.com]
> Sent: 11 January 2012 10:49
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Patching
>
> I'll try and answer this but it's best to seek some other opinions too.
>
> 1. The order of p
he Wix team)
This mailing list's archives
Wix docs
-Original Message-
From: Sanjay Poria [mailto:sanjay.po...@xanalys.com]
Sent: 10 January 2012 23:18
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Patching
I am in the process of writing an installer for a company pro
I am in the process of writing an installer for a company product (we were
previously using Installshield). Once, released we will need the produce
patches for bug fixes and enhancements. The expectation that these patches will
consist of simply updating some of the released files and/or adding
You can ship your patches as plain .msp files or you can wrap the .msp files
in another Bundle (great if you need to apply multiple patches or want to
show a custom UI).
On Sat, Mar 26, 2011 at 5:28 AM, Sean Farrow
wrote:
> Hi:
> I'm currently writing a bundle using burn. Later on we will need to
Hi:
I'm currently writing a bundle using burn. Later on we will need to write and
release patches.
As I am using burn, can I use plain .msp/msu files or do I have to use a .exe
file?
Any help appreciated.
Regards
Sean.
--
: Arun Kumar [mailto:arun_jku...@persistent.co.in]
Sent: 10 March 2011 09:20
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Patching Merge module
Hi All,
I am building WIX MSI that has integrated Merge Module.
Now I am creating patches for this MSI.
I know that I can
Hi All,
I am building WIX MSI that has integrated Merge Module.
Now I am creating patches for this MSI.
I know that I can specify ComponentRef's in my patch.wxs file but is there any
way to provide patch for the integrated Merge Module?
Thank You all in advance.
Regards,
AK.
DISCLAIMER
===
olset.
Subject: Re: [WiX-users] Patching Using Purely Wix
Would creating a pure Wix patch from administrative installations work for
you ? It's what we do here.
This gives you an idea of the process.
http://blogs.msdn.com/b/pmarcu/archive/2008/05/30/patching-something-you-did
n
t-build-with-wix-using
Liam Flanagan [mailto:l...@dyalog.com]
Sent: 16 February 2011 12:46
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Patching Using Purely Wix
Hello All,
I've been wondering if it's possible to create minor patches using the
"purely wix" method, however only using
Hello All,
I've been wondering if it's possible to create minor patches using the
"purely wix" method, however only using the baseline and QFE MSI packages
instead of requiring the original source files and structure that the MSIs
were built from. I want have the benefits of purely wix patching
t Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer
-Original Message-
From: Tom Crozier [mailto:tcroz...@rackwise.com]
Sent: 03 February 2011 20:13
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Patching multiple major upgrade releases with
All -
I have multiple versions of a product released in the field
that I need to upgrade with a patch. The installer that all the versions are
all based on can perform a major upgrade from a previous version. I believe
they should have used the same product id but they don't beca
ience Park,
Glasgow G20 0SP
Email Disclaimer
-Original Message-
From: Henk Roos [mailto:henk.r...@aricent.com]
Sent: 16 November 2010 09:39
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Patching and properties
Hi there,
Is it possible to pass a property value somehow to a
Hi there,
Is it possible to pass a property value somehow to a custom action when
installing a new patch (in stead of passing it with the command line)? And also
I want to know if it is possible to get the patch version being installed with
a custom action. I did run the following command : "mi
included in the patch.
-Original Message-
From: Christopher Painter [mailto:chr...@deploymentengineering.com]
Sent: 05 October 2010 13:40
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Patching with WiX
I can certainly build through to completion and do
ead a really good thread that deserves
attention? E-Mail Me
- Original Message
From: Peter Shirtcliffe
To: wix-users@lists.sourceforge.net
Sent: Tue, October 5, 2010 4:11:31 AM
Subject: Re: [WiX-users] Patching with WiX
This is the same situation as we have here.
It's preferable, if
tains useful info too.
-Original Message-
From: Christopher Painter [mailto:chr...@deploymentengineering.com]
Sent: 04 October 2010 18:03
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Patching with WiX
I was wondering if anyone could provide me with any links or pointers fo
I was wondering if anyone could provide me with any links or pointers for the
following story.
Foo.msi is a large ( 15,000 files ) installer that is currently build with
InstallShield and services via Major Upgrades.
Foo.msi's file comes from a couple dozen builds and the upstream build team
d
hi Sunkesula, Srivardhan,
how your question is merged in to my query? is there any problem ?
srinivas
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/setting-the-existing-apppool-to-my-virtual-directory-other-than-than-the-default-apppool-tp5234
Place the SampleComponent component in its own Fragment.
-Original Message-
From: Sunkesula, Srivardhan [mailto:srivardhan.sunkes...@netapp.com]
Sent: Tuesday, June 29, 2010 2:57 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] patching a single file
Hi
Hi,
I would like to create a patch which can install a single
file/component.
I specified the component, say "SampleComponent" which I want to
patch as shown below:
But this is patching all the components in the product.
Can anyone
Does this thread help:
http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg27915.htm
l
?
-- Yan
-Original Message-
From: d8x...@hotmail.com [mailto:d8x...@hotmail.com]
Sent: Tuesday, 08 June, 2010 21:49
To: Wix-Users
Subject: [WiX-users] Patching multiple instances of
I am using the new Wix patching process to create my MSPs. I am having trouble
with my patches working on multiple instances of my product. The patch
complains that the product is not installed. Using the patchwiz process
patching multiple instances worked. The patch runs against the default in
or Windows Installer XML toolset.
Subject: Re: [WiX-users] Patching Base Versions
Here is one example where you can try insert additional targets (bases)
http://schemas.microsoft.com/wix/2006/wi";>
http://www.myco.com";
Classificatio
OptimizedInstallMode="yes" />
-Original Message-
From: XorPtr [mailto:reaper4...@gmail.com]
Sent: Tuesday, June 01, 2010 4:22 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Patching Base Versions
.
-Original Message-
From: XorPtr [mailto:reaper4...@gmail.com]
Sent: Tuesday, June 01, 2010 4:22 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Patching Base Versions
I had a question about whether a feature is supported and haven't seen any
WiX documentation that really answe
I had a question about whether a feature is supported in WiX or not. I
haven't seen any WiX documentation that really answers my question.
Basically I was curious as to how patches could be installed and supersede
each other based on the base used to create the patch.
For example if I have Prod
I had a question about whether a feature is supported and haven't seen any
WiX documentation that really answers my question. Basically I was curious
as to how patches could be installed and supersede each other based on the
base used to create the patch.
For example if I have Product v1.0.3 dir
Hi,
Was wondering if somebody could help. I'm trying to create a patch (MSP)
for my installation and have being following the tutorial on
http://www.tramontana.co.hu/wix/lesson4.php
Which has been very helpful.
I had the original wixpdb for my original installation, which was handy :)
So followi
erate a .wixmst.
-Original Message-
From: Wilson, Phil [mailto:phil.wil...@invensys.com]
Sent: Wednesday, March 10, 2010 3:15 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Patching a single component
I'm not sure where this is specified in W
-
From: Wilson, Phil [mailto:phil.wil...@invensys.com]
Sent: Wednesday, March 10, 2010 3:15 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Patching a single component
I'm not sure where this is specified in WiX patching, but the PCP file has a
TargetI
Glass [mailto:agl...@laserfiche.com]
Sent: Wednesday, March 10, 2010 1:46 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Patching a single component
As part of my first foray into the world of patching, I have been tasked with
creating hotfix patches for our product. As
As part of my first foray into the world of patching, I have been tasked with
creating hotfix patches for our product. As part of the daily build, the
version numbers for all files in the product are incremented, but I only want
to patch the specific files that were fixed as part of the hotfix.
In article
<89030b4a18eccd45978a3a6b639d1f24030ac82...@fl01exmb01.trad.tradestation.com>,
Tony Juricic writes:
> At which point in the patching process are custom actions that are
> executing the updated ones?
If they are custom actions that execute out of installed files, the
updated act
At which point in the patching process are custom actions that are executing
the updated ones?
I have custom actions that execute before and after PatchFiles action.
Custom action executing before PatchFiles finds MSI DB already transformed.
Based on that I would expect that table containing cu
1 - 100 of 228 matches
Mail list logo
