kirannhegde wrote
> 1. What happens when you apply the patches outside of Burn?
> 2. Also, how did you make sure that Patch 2 is in the view when you
> uninstalled Patch 3?
> 3. Do you have a verbose windows installer log file?
Hi Kirian
1. Applying the patches only workes fine.
2. I assumed burn
Hello,
What happens when you apply the patches outside of Burn?
Also, how did you make sure that Patch 2 is in the view when you uninstalled
Patch 3?
Do you have a verbose windows installer log file?
Regards,
Kiran Hegde
--
View this message in context:
http://windows-installer-xml-wix-tool
Hello Experts,
Deploying Patches via burn, supersede is on.
*Deploying Patch 1.0.1.0 -> Changes apply in installation, 'view
installed updates' shows patch 1.0.1.0
*Deploying Patch 1.0.2.0 -> Changes apply in installation, 'view
installed updates' shows patch 1.0.2.0
*Dep
Does anyone has any other thoughts?
Regards,
Kiran Hegde
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-sequencing-problem-Small-update-a-supseding-hotfix-tp7598304p7598398.html
Sent from the wix-users mailing list archive at Nabble.com.
a
> stephen.tunney@
> 519-880-7463 Office
> NUANCE.COM
> The experience speaks for itself (tm)
>
> -Original Message-
> From: kirannhegde [mailto:
> kirann.hegde@
> ]
> Sent: December-01-14 11:42 PM
> To:
> wix-users@.sourceforge
> Subject: Re: [W
n
Waterloo, Ontario, Canada
stephen.tun...@nuance.com
519-880-7463Office
NUANCE.COM
The experience speaks for itself (tm)
-Original Message-
From: kirannhegde [mailto:kirann.he...@gmail.com]
Sent: December-01-14 11:42 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Patch
Hello,
Thanks for the response.
I am not using Wix to build my patch.
I am using msimsp to build my patch.
Another follow up question:
Is a superseding hotfix meant to replace everything from supserseded
hotfixes , even if that results in downgrade of files?
Regards,
Kiran Hegde
--
View t
ings manually at the moment to get the
new CustomAction into the patch.
From: kirannhegde [kirann.he...@gmail.com]
Sent: December 1, 2014 1:15 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Patch sequencing problem - Small update + a supseding
Hello All,Here is my scenario:Base product has a version of 1.0-I have a
small update(QFE) which has a sequence number of 1.0.6.0The small update
contains a file named PatchCustomActions.dll with a version of 1.0.3.0Patch
code: {2BA41362-74A7-427D-A219-93CBFF4C5844}The small update also contains a
-Original Message-
From: Phil Wilson [mailto:phildgwil...@gmail.com]
Sent: Tuesday, October 28, 2014 1:35 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Patch uninstall from APR on Windows 2012 R2 going into
repair mode
Just cover the bases, I assume you are
8, 2014 8:07 AM
> To: General discussion about the WiX toolset.
> Subject: [WiX-users] Patch uninstall from APR on Windows 2012 R2 going into
> repair mode
>
> Everyone,
>
> I was doing patch testing on Windows 2012 R2 and noticed that my patches were
> not uninstalling
& Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
|jocoo...@jackhenry.com
-Original Message-
From: Skildum, Mat [mailto:mathew.skil...@aspect.com]
Sent: Tuesday, October 28, 2014 8:07 AM
To: General discussion about the WiX toolset.
Subject: [WiX-users] Patch uninstall from AP
Everyone,
I was doing patch testing on Windows 2012 R2 and noticed that my patches were
not uninstalling when targeted through APR. Instead maintenance mode was
launched and the user was prompted with the standard modify, Repair, or
uninstall option for the product. I can remove patches just
A couple of things to keep in mind:
1. Patches are applied at the feature level, so that entire feature is
patched. If you had separate features you could do a patch install
command with a REINSTALL= which would leave the
other features alone, assuming they weren't being patched. A patch is
sort
I've solved this particular issue. The solution was to move the WebConfigCmp
into a separate sub-feature like below. My next step will be to partition
AppliationWebFiles components into separate so that I can deliver
them selectively in Small Patches which is my ultimate goal.
I have a very similar problem. I've created a single Feature install that
includes a large set of files to install along with some other components
such as one to install and modify the web.config. My new install works
fine, however my Patch is trying to re-install the component for the
web.confi
eptember 25, 2014 12:11 PM
To: [hidden email]
Subject: [WiX-users] Patch question (been a while since I did patches, and
haven't used WIX for Patches)
Here is what I did:
created:
patch\rtm which holds the admin install of the RTM version of our
software (WIX 3.5 MSI 3.0)
patch\upp
Jack Henry & Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
|jocoo...@jackhenry.com
-Original Message-
From: Steve-Ogilvie [mailto:steven.ogil...@titus.com]
Sent: Thursday, September 25, 2014 12:11 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Patch questio
Here is what I did:
created:
patch\rtm which holds the admin install of the RTM version of our
software (WIX 3.5 MSI 3.0)
patch\upp which holds the latest hotfix admin install of our
software (WIX 3.5, MSI 3.0)
patch\tempholds icons/binaries that are internal to MSI
rtm
: General discussion about the WiX toolset.;
wix-users-requ...@lists.sourceforge.net
Subject: [WiX-users] PATCH REINSTALL=ALL REINSTALLMODE=amus
Hi guys and girls :)
Is possible to enforse PATCH REINSTALL=ALL REINSTALLMODE=amus when installing a
patch without using the command line arguments, like
Hi guys and girls :)
Is possible to enforse PATCH REINSTALL=ALL REINSTALLMODE=amus when installing a
patch without using the command line arguments, like when I double click the
msp?
Thanks
Christoff le Roux
This information is intended only for the person or entity to which it is
addressed a
Ok, figured out what was wrong, operator error . I had my Upgrade and Target
sourcefiles reversed. After I fixed that it worked as expected
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-Creation-Properties-example-in-manual-not-working-
I am looking in to creating patches with WiX and therefore I am starting with
the basics of both:
Using Patch Creation Properties and
Using Purely WiX
I am currently using the 3.7 released version of WiX and following the exact
example for the 'Using Purely WiX' from the following documentation wo
If that's the only info you know, then create a log of the patch install
and post it for people to see.
Common reason: You deleted a component (that's not allowed) and the patch
process went into "advertised" mode and nothing was patched.
Phil Wilson
On Tue, Oct 29, 2013 at 1:47 AM, Ravishankar
Hi,
I have my main installer built on XP(32 bit) Profession, Visual Studio 2008
now am creating patches using the patchwiz method and created a new
build on Win-7(64 bit) and Visual Studio 2010
The patch is getting created with all the differential and new files,
but when i run the *.msp its not
See if this helps:
http://blogs.msdn.com/b/heaths/archive/2009/04/12/patch-applicability.aspx
Phil Wilson
On Thu, Aug 22, 2013 at 3:47 AM, Swaroop Kare
wrote:
> Hi,
>
>
>
>I am able to make Patch1 based on
> http://wix.tramontana.co.hu/tutorial/upgrades-and-modularization/patchwo
> rk but
Hi,
I am able to make Patch1 based on
http://wix.tramontana.co.hu/tutorial/upgrades-and-modularization/patchwo
rk but I am falling back when making subsequent workable patches. Can
any one tell me if I am missing any step while I am doing Patch2.
Step1: Add new components into wix and up
Thank you for the response. It is very helpful.
Phill
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-Best-practice-using-fragments-tp7587660p7587722.html
Sent from the wix-users mailing list archive at Nabble.com.
-
he two versions, it
will not be included in the patch (doesn't matter if it was included or not).
-Blair Murri
> From: jocoo...@jackhenry.com
> To: wix-users@lists.sourceforge.net
> Date: Mon, 29 Jul 2013 18:41:19 +0000
> Subject: Re: [WiX-users] [Patch] Best practice using f
acob.hoo...@greenheck.com]
Sent: Monday, July 29, 2013 1:17 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] [Patch] Best practice using fragments
I think the part you are missing is " all changed components from that fragment
will show up in your patch". I
I think your right. I had noticed that phrase, but was not certain of my
interpretation of it. I agree that I don't know why I would ever deploy a
subset of "changed" files in a ComponentGroup. So in that case I guess I am
ready to move on in testing my new setup.
Thanks.
Phil
--
View this me
, July 29, 2013 11:40 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] [Patch] Best practice using fragments
I am relatively new to WiX 3.7 and MSI (and having lots of fun with the great
WiX documentation and information available in the forum). As I get my BA/msi
functional I am t
I am relatively new to WiX 3.7 and MSI (and having lots of fun with the great
WiX documentation and information available in the forum). As I get my
BA/msi functional I am trying to review best practices and I came across a
post at:
http://stackoverflow.com/questions/471424/wix-tricks-and-tips
In
Okay, but given the scenario when a bundle contains only one MSP, this
doesn't seem good...
How can I get it to fail the bundle?
Otherwise, I get a bundle ARP entry but no patch installed...
Thanks,
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.c
Hi,
Can anyone tell my why a patch bundle installs successfully even though the
patch inside didn't?
If I run the MSP on an invalid RTM product, I get the usual message.
>From the log:
[07AC:0B2C][2013-07-24T11:14:47]i201: Planned package: cs201022_HotFix00,
state: Absent, default requested: Pr
@Rob,
I've tried the Update element but the bundle still shows up in the main list
rather than the 'View installed updates' list..
Please advise...
Thanks,
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-not-visible-in-ARP-if-MSI-install
which is a solution that will
scale).
Blair Murri
> Date: Tue, 9 Jul 2013 04:20:37 -0700
> From: christian.hennig@wincor-nixdorf.com
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] [WIX-users] Patch in Wix 3.6 is empty. warning
> PYRO1079: The cabinet '**
iles,
e.g. a CRC code, which gives a hint that the file was modified.
So maybe our only chance is to wait for the diff-feature for MSI files.
Best regards
Christian
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WIX-users-Patch-in-Wix-3-6-
On 01-Jul-13 03:44, Kryschan wrote:
> We are really looking forward to a solution for this issue.
Then please file a bug with sufficient detail to reproduce the problem.
Obviously, WiX needs two different files to be able to diff them, so you
need to describe in more detail what you're doing that
Start here: http://msdn.microsoft.com/library/windows/desktop/aa372388.aspx
> Date: Tue, 2 Jul 2013 09:58:09 +0530
> From: ravishankar.krishnasw...@idsnext.com
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Patch Installation Privileges
>
> Hi ,
>
> I
Hi ,
I have installed our main Installer(msi) with administrator rights, now i want
to install the *.msp with Standard Users Rights(Non-administrator)
Thanks and Regards
Ravi Shankar
--
This SF.net email is sponsore
off of the "official" MSI packages
(and their contents) that were deployed.
-Original Message-
From: Kryschan [mailto:christian.hennig@wincor-nixdorf.com]
Sent: Monday, July 01, 2013 2:44 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] [WIX-users] Patch in
it to avoid checking for
differences in files originated from the same location.
That was definitely working with WiX 3.5.
We are really looking forward to a solution for this issue.
Christian Hennig
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WIX-
gt; From: jacob.hoo...@greenheck.com
> To: wix-users@lists.sourceforge.net
> Date: Wed, 12 Jun 2013 17:10:51 +0000
> Subject: [WiX-users] Patch Creation
>
> When using the "old way" of creating patches
> (http://wix.sourceforge.net/manual-wix3/patch_building.htm) the documen
You automatically get a "free" upgrade RelatedBundle matching the
UpgradeCode. That way you're always able to upgrade your bundles. MSI
doesn't require this with MSIs which catches people by surprise sometimes
when they figure out at v2 that they can't upgrade v1.
On Sat, Jun 15, 2013 at 6:02 AM
Thanks.. do I also need RelatedBundle set in the MSI bundle or will suffice in the MSP bundle?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-not-visible-in-ARP-if-MSI-installed-via-Bundle-tp7586533p7586583.html
Sent from the wix-users ma
You can make a patch bundle show up in "View install updates". I think it's
the Update element child of Bundle that does that. Also, Burn does a lot of
stuff to ensure the MSP is applied correctly to all products it targets.
Just double clicking on an MSP doesn't guarantee the same.
Basically, I t
Having spent the morning playing around with this, I would agree that patch
bundles are probably the best solution...
It would be nice if a purely patch bundle showed up in 'View installed
updates' ...
James.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n
undle one carefully. Until we migrate it
works for us.
Dave
-Original Message-
From: rowbot [mailto:james.row...@microfocus.com]
Sent: 14 June 2013 11:45
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Patch not visible in ARP if MSI installed via Bundle
Indeed, if I r
Indeed, if I rename :
HKEY_CLASSES_ROOT\Installer\Products\4109501100F01FEC\ProductName
neither the MSI or the MSP are visible in ARP (!)
This is a real problem...
Anyone, any input?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabbl
I think if you delete the key it and its updates would not be visible in ARP.
-Original Message-
From: rowbot [mailto:james.row...@microfocus.com]
Sent: 14 June 2013 10:18
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Patch not visible in ARP if MSI installed via Bundle
Yes, patch bundle is an option but if it's just installing one MSP, a EXE
around it seems a bit clunky (and it's also another UI that needs
creating/maintaining)
I wonder if we don't hide the MSI entry (Visible="yes")... is there some way
of deleting the MSI's Uninstall key?
--
View this messa
uninstall from arp. If so it's yet another
reason for us to ditch our custom chainer.
Dave
-Original Message-
From: rowbot [mailto:james.row...@microfocus.com]
Sent: 14 June 2013 09:40
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Patch not visible in ARP if MSI instal
I've installed an MSI using a Bundle, and then installed an MSP..
The MSP is not visible in 'View installed updates' (!)
I presume this is because the MSI is installed with ARPSYSTEMCOMPONENT=1
This is not good news
Is there a fix/workaround?
Thanks,
--
View this message in context:
When using the "old way" of creating patches
(http://wix.sourceforge.net/manual-wix3/patch_building.htm) the documentation
states that /PatchCreation/Family/@SequenceStart must be greater than the last
sequence in the file table. If I omit this attribute, I end up with a file
with a sequence o
to properties and
> use omus mode to add new registry. We do not care if all registry is
> overwritten since we write the same values as before.
>
>
> Message: 1
>> Date: Fri, 24 May 2013 15:02:00 +0530
>> From: Ravishankar
>> Subject: [WiX-users] Patch overwriting
same values as before.
Message: 1
> Date: Fri, 24 May 2013 15:02:00 +0530
> From: Ravishankar
> Subject: [WiX-users] Patch overwriting registry entries
> To: "General discussion for Windows Installer XML toolset."
>
> Message-ID: <519f3390.4060...@idsnext.
Hi,
Are the registry keys filled with properties entered or modified by the user?
If so, are the registry keys set to default in your patch case?
Am 24.05.2013 um 11:32 schrieb Ravishankar
:
> Hi All,
> My main installer creates some registry entries(Database
> ServerName,Database Name etc)
Hi All,
My main installer creates some registry entries(Database
ServerName,Database Name etc)
I have created a patch using the pcp method and when installing the
patch its overwriting the registry entries created by the main installer
Can anyone please help me out.
Thanks and Regards
Ravi
--
Hi All,
My Main installer creates ODBC DSN and few registry entries
after the apply the patch some of these entries are getting deleted.
Any help?
Thanks and Regards
Ravi
--
Try New Relic Now & We'll Send You this Coo
You should be fine if you wrote your code in a typical way. A
patch is basically a repair operation. As long as the Components with the
updated executables also contain the NativeImage elements then the Windows
Installer will know to update the Component and the NativeImage custom
action will know
Hi all - we have an MSI with many DLL and a couple of EXE assemblies, the
latter of which are nGen'd via netfx:NativeImage.
We are getting ready to create a patch MSP using torch/pyro and wondering if we
need to do anything explicit to re-nGen these EXE's. Thanks for any info !
-Rob
to be tested.
-Original Message-
From: Uma Harano [mailto:uhar...@esri.com]
Sent: Tuesday, October 16, 2012 10:01 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Patch issue
I read in the SDK that the companion file cannot be the key path of the
[mailto:kbis...@adobe.com]
Sent: Monday, October 15, 2012 5:42 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Patch issue
You could try making it a companion file in your patch.
So, the installation state of a companion file depends not on its own file
n that the condition that required the reboot
won't occur again.
-Original Message-
From: abhijit chakraborty [mailto:abhi.chak.ju...@gmail.com]
Sent: 16 October 2012 11:23
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Patch installation asks for a reboot
Hi,
We are crea
Hi Matt
The edited msi that the msp targets does the correct 10.1.1 version.
But the msp is still not patching it.
I will try the companion file idea that Kajal explained.
Thanks!
On Oct 15, 2012, at 5:32 AM, "Matt O'Connell" wrote:
> Use the version lying technique: Change the version of t
t.
> Hence the mst removing the version no. will become ineffective.
>
> -Original Message-
> From: Uma Harano [mailto:uhar...@esri.com]
> Sent: Monday, October 15, 2012 5:33 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Patch
[mailto:uhar...@esri.com]
Sent: Monday, October 15, 2012 5:33 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Patch issue
Hi Kajal
Thank you for your email.
Unfortunately the mst has already been released to our customers. We are now
trying to release the msp
Use the version lying technique: Change the version of this FileId to
10.1.1 in your patch upgrade image by editing the msi in orca. Then
re-build the patch pointing to your edited MSI.
When the patch installs on top of the localised version it won't matter
that the transform has removed this a
released mst.
Thanks
Uma-
-Original Message-
From: Kajal Kumar Biswas [mailto:kbis...@adobe.com]
Sent: Sunday, October 14, 2012 10:33 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Patch issue
When the mst is applied, the msi cache is not updated with
how exactly you are trying to create the mst file?
-Original Message-
From: Uma Harano [mailto:uhar...@esri.com]
Sent: Sunday, October 14, 2012 3:52 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Patch issue
Hi
I have a patching issue I need help with
Hi
I have a patching issue I need help with. Version 10.1 of my msi installs a dll
with version 10.1.0. This is the also the version listed in the File table of
the msi for this dll. This msi is the English setup. I have embedded msts in
this msi that localizes the dialogs for this msi. There wa
ation.
If all seems well examine a verbose log produced from applying the patch.
-Original Message-
From: Muzikayise Flynn Buthelezi [mailto:muzkay...@gmail.com]
Sent: 03 October 2012 21:55
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Patch not insta
gt; Justin Hull
> Sr. Developer
>
>
> Maximizing Asset Performance
> (864) 679-3513 Office
>
>
> -Original Message-
> From: Justin Hull [mailto:justin.h...@assetpoint.com]
> Sent: Wednesday, October 03, 2012 12:09 PM
> To: General discussion for Windows Installer XML
9-3513 Office
-Original Message-
From: Justin Hull [mailto:justin.h...@assetpoint.com]
Sent: Wednesday, October 03, 2012 12:09 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Patch not installing files.
I've run into a strange issue with a patch that m
I've run into a strange issue with a patch that maybe I can get some direction
from this group.
I generate a patch file (msp) performing the following commands:
"C:\Program Files\WixEdit\wix-3.0.5419.0\candle.exe"
"J:\Tw8-2z\Pro02\Disks\Xi\TabWareXiTools8202.wxs" -ext W
On 25-Sep-12 09:55, Parker, Steven wrote:
> Just to update I have found that the problem seems to stem from the torch
> call and if I use the wixmst file generated by 3.5 it creates the patch fine.
Can you post the .wixmsts in a bug?
--
sig://boB
http://joyofsetup.com/
al Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Thursday, September 27, 2012 10:51 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Patch installing component with Not Installed condition
The Condition is only evaluated once unless the Co
The Condition is only evaluated once unless the Component is marked
Transitive='yes'
On Thu, Sep 27, 2012 at 9:03 AM, Tom Crozier wrote:
> I have an installer that contains the following component.
>
>Guid="{226F7E2A-2FBD-2ed4-B355-52C80E95A212}" KeyPath="yes">
>
>
I have an installer that contains the following component.
This runs fine during the initial install. Now I have created a patch and have
not modified this component but it is trying to run the code again even though
the condition states NOT Installed.
b -out %OutputFolder%\PROGRAMpatch32.wixmst
Not sure if this helps at all
-Original Message-
From: ChipSlog [mailto:steven.par...@nikonmetrology.com]
Sent: 25 September 2012 14:34
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] [WIX-users] Patch in Wix 3.6 is empty. warning
P
empty cab file warning.
Thanks in advance.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WIX-users-Patch-in-Wix-3-6-is-empty-warning-PYRO1079-The-cabinet-cab-does-not-contain-any-files
Sent: 17 September 2012 16:41
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Patch failure when using non-whole files
Hi,
I have the same issue..
How can I mark certain files as a full-file patch?
Thanks,
--
View this message in context:
http://windows-installer-xml-wix-tool
Hi,
I have the same issue..
How can I mark certain files as a full-file patch?
Thanks,
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-failure-when-using-non-whole-files-tp701419p7580576.html
Sent from the wix-users mailing list archive
Small updates do not require changing the product code! This forces a
major update and thus your update is massive:-) . All msi file have a
package code which should probably be left to generate automatically.
This should be changed in any event.
As an aside, if you can find a reason to update
In the WIX of Product, we do not use PackageCode, as far I remember. It was
deprecated
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-to-update-version-of-installed-product-tp7579458p7579483.html
Sent from the wix-users mailing list archive at
Hi Moc
Thanks for the tips. No, I only changed ProductCode with a new GUID and
updated in all other tables e.g. Registry, INIFile etc.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-to-update-version-of-installed-product-tp7579458p7579482.ht
WholeFilesOnly="yes" change to "no"
Order="2" change to "1"
patch runnup issue - did you change the package code for the updated msi?
On 18/07/2012 12:34, Farrukhw wrote:
> Thanks all for your replies. I've just posted my resultant patch script here:
> http://windows-installer-xml-wix-toolset.6
Thanks all for your replies. I've just posted my resultant patch script here:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-can-t-update-installed-product-and-shows-Change-Repair-dialog-td7579479.html
but with some issues and I need help in these.
Thanks
--
View this messag
Hi Guys,
I'm building a patch using PCP, according to this tutorial:
http://wix.sourceforge.net/manual-wix3/patch_building.htm
http://wix.sourceforge.net/manual-wix3/patch_building.htm
I'v two MSI (extracted as Admin installs)
1. 8.11.9.225 (This is my target to update)
2. 8.11.9.353 (The latest
: [WiX-users] Patch to update version of installed product?
Thanks anyway Neil for giving time
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-to-u
pdate-version-of-installed-product-tp7579458p7579470.html
Sent from the wix-users mailing list
SI.
There might be other ways too - I don't use the MSI UI myself.
-Original Message-
From: Farrukhw [mailto:farru...@gmail.com]
Sent: 17 July 2012 14:11
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Patch to update version of installed product?
Peter,
I just tr
Peter,
I just tried this:
http://schemas.microsoft.com/wix/2006/wi";>
and it worked. It changed the version that 4 digit version successfully. But
only problem I faced is when I launched the msp file, it showed Customize
Dialo
@lists.sourceforge.net
Subject: Re: [WiX-users] Patch to update version of installed product?
Thanks again...
I was reading this article about patch restrictions:
http://wix.sourceforge.net/manual-wix3/patch_restrictions.htm
and it mentions following:
Small updates: do not change the ProductVersion
Thanks anyway Neil for giving time
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-to-update-version-of-installed-product-tp7579458p7579470.html
Sent from the wix-users mailing list archive at Nabble.com.
-
Sorry I can't help, I never do patches I find it is easier to stick with major
upgrades for all releases.
Neil
-Original Message-
From: Farrukhw [mailto:farru...@gmail.com]
Sent: 17 July 2012 13:36
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Patch to update versi
Thanks Neil,
But that's a full product upgrade. My task is to generate a patch which
would update the Version info of installed product.
I just tried this:
http://schemas.microsoft.com/wix/2006/wi";>
and it worked. It changed
[mailto:farru...@gmail.com]
Sent: 17 July 2012 13:08
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Patch to update version of installed product?
Thanks again...
I was reading this article about patch restrictions:
http://wix.sourceforge.net/manual-wix3/patch_restrictions.htm
and it mentions
Thanks again...
I was reading this article about patch restrictions:
http://wix.sourceforge.net/manual-wix3/patch_restrictions.htm
and it mentions following:
Small updates: do not change the ProductVersion property of a target product
and typically represent a small subset of files to be updated.
Note windows installer only supports 3 part version numbers, so in your example
they are both the same version (i.e. 9.4.5).
Neil
-Original Message-
From: Farrukhw [mailto:farru...@gmail.com]
Sent: 17 July 2012 11:55
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Patch to
1 - 100 of 324 matches
Mail list logo
