You could also split your optional features into separate MSIs and use Burn to
control their installation behaviour, which may be easier in the long run than
trying to fight what windows installer is intended to do. You would probably
need a custom BA though.
-Original Message-
From:
oper [mailto:jocoo...@jackhenry.com]
> Sent: Monday, September 29, 2014 1:54 PM
> To: General discussion about the WiX toolset.
> Subject: Re: [WiX-users] WiX Upgrade Questions
>
> If you used the remember pattern for your install location property,
> http://robmensching.com/blog/
-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: Monday, September 29, 2014 1:54 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] WiX Upgrade Questions
If you used the remember pattern for your install location property,
http://robmensching.com/blog
If you used the remember pattern for your install location property,
http://robmensching.com/blog/posts/2010/5/2/the-wix-toolsets-remember-property-pattern/,
then yes. Otherwise, not so much.
If the service no longer starts, it has a bug or there's a problem with your
service authoring. A pro
e: http://www.firegiant.com/
>
>
>
> -Original Message-
> From: Phil Wilson [mailto:phildgwil...@gmail.com]
> Sent: Tuesday, September 16, 2014 10:56 AM
> To: General discussion about the WiX toolset.
> Subject: Re: [WiX-users] WIX : Upgrade Issue
>
> Regarding the &quo
: General discussion about the WiX toolset.
Subject: Re: [WiX-users] WIX : Upgrade Issue
Regarding the "wrong custom action" issue: there have been problems in that
area with managed custom actions where the uninstall part of the upgrade runs
first, loading the assembly for that ol
Regarding the "wrong custom action" issue: there have been problems in
that area with managed custom actions where the uninstall part of the
upgrade runs first, loading the assembly for that older custom action.
When the new install runs and the loading code comes to load the new
assembly the runti
Hi John,
Thanks for the reply.The upgrade used to work well previously..Also i am
sure, that the changes that was done later on, does not break the upgrade.
I already have your suggested approach #2 implemented when the major upgrade
was implemented.
I have a custom action which takes a backup o
If no modifications to the config files have been made since they have been
installed, they will be deleted with your upgrade scheduling before the upgrade
install.
You can: 1) tweak the timestamp on the config file(s) so they are preserved;
or 2) have a custom action read the file data to be
9-639-1680
-Original Message-
From: Sanjay Rao [mailto:s...@noida.interrasystems.com]
Sent: Monday, January 17, 2011 10:30 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Wix upgrade process does not consider 4th part of the
version string
Hi,
This is not a better solut
>
>> May be I am missing the point but surely the WiX install has adopted the
>> same approach, you just happen to set part 4 to 0 and don't release two
>> versions on the same day. If you have continuous integration system I am
>> struggling to see an alternative.
>&g
se'
> or 'Beta release' logo when installing as well :)
>
> Albert van Peppen
>
> -Oorspronkelijk bericht-
> Van: Christopher Painter [mailto:chr...@deploymentengineering.com]
> Verzonden: zondag 16 januari 2011 18:18
> Aan: General discussion for Win
: Mon 17/01/2011 11:37
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Wix upgrade process does not consider 4th part of the
version string
For the reason mentioned, we use the bootstrapper for handling the correct
action on the fourth part of the version s
an Peppen
-Oorspronkelijk bericht-
Van: Christopher Painter [mailto:chr...@deploymentengineering.com]
Verzonden: zondag 16 januari 2011 18:18
Aan: General discussion for Windows Installer XML toolset.
Onderwerp: Re: [WiX-users] Wix upgrade process does not consider 4th part of
the version str
7 January 2011 02:47
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Wix upgrade process does not consider 4th part
of the version string
I saw you're reply later and was going to get to it later (er, now).
Personally, I would chose to have an error that
; versions on the same day. If you have continuous integration system I am
> struggling to see an alternative.
>
> Neil
>
> -Original Message-
> From: Rob Mensching [mailto:r...@robmensching.com]
> Sent: 16 January 2011 18:12
> To: General discussion for Windows Instal
27;t release two
versions on the same day. If you have continuous integration system I am
struggling to see an alternative.
Neil
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: 16 January 2011 18:12
To: General discussion for Windows Installer XML toolset.
Sub
; Chris
>
> Christopher Painter, Author of Deployment Engineering Blog
> Have a hot tip, know a secret or read a really good thread that deserves
> attention? E-Mail Me
>
>
>
> ----- Original Message
> From: Rob Mensching
> To: General discussion for Windows Instal
toolset.
Subject: Re: [WiX-users] Wix upgrade process does not consider 4th part
of the version string
Terrifying. You must be in some really controlled environments for that
to work out well.
The Windows Installer (for whatever reason) chose to ignore the 4th
version.
It boggles my mind that
secret or read a really good thread that deserves
attention? E-Mail Me
- Original Message
From: Rob Mensching
To: General discussion for Windows Installer XML toolset.
Sent: Sun, January 16, 2011 10:55:00 AM
Subject: Re: [WiX-users] Wix upgrade process does not consider 4th part of t
Terrifying. You must be in some really controlled environments for that to
work out well.
The Windows Installer (for whatever reason) chose to ignore the 4th version.
It boggles my mind that "management" gets to decide a versioning scheme that
won't work. You might as well pick a different instal
I have a similar scenario and my workaround is to allow same version
upgrades. This means 3.0.1.14900 will upgrade 3.0.1.14500 (but it also
means 3.0.1.14500 will upgrade 3.0.1.14900 which might be undesirable).
In WiX 3.5 you can do this by setting
MajorUpgrade/@AllowSameVersionUpgrades - otherwi
Hi,
read this thread. Maybe this is what you need:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Setup-upgrade-needs-to-care-for-4th-part-of-version-number-td3250189.html
Dirk
On Fri, Jan 14, 2011 at 23:55, Wilson, Phil wrote:
> That's a Windows Installer limitation on upgrad
That's a Windows Installer limitation on upgrades.
http://msdn.microsoft.com/en-us/library/aa369786(v=vs.85).aspx
"Note Windows Installer uses only the first three fields of the product
version ..."
Phil Wilson
-Original Message-
From: Sanjay Rao [mailto:s...@noida.interrasyste
Hahaha nevermind... I see that I totally got it backwards... I reversed my
OnlyDetects below and it works great... You rock... Sorry!
-Jeremy
On Wed, Jul 14, 2010 at 9:20 AM, Jeremy Rimer wrote:
> Blair, as always, thanks for your replies! Unfortunately, this time I came
> up empty :(.
>
> I di
Blair, as always, thanks for your replies! Unfortunately, this time I came
up empty :(.
I did the following but still ended up with a duplicate of my applications
installed in Add/Remove Programs after the Installer finished:
- I modified my upgrade element as follows:
===
In the UpgradeVersion element, OnlyDetect does exactly what it suggests: it
only detects all matching products (setting the indicated property with the
list of found ProductCodes), suppressing passing those ProductCodes to
RemoveExistingProducts. Set OnlyDetect to "no" for those properties that
con
Your assembly is not loading. There could be a myriad of reasons causing
that. You'll need to debug the assembly loading issue first. Searching the
internet should give you the tools to debug assembly load failures.
On Tue, Dec 1, 2009 at 2:53 AM, MYFLEX wrote:
>
> we have upgrade all the visual
[mailto:queryl...@yahoo.com]
Sent: Wednesday, September 09, 2009 10:56 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WIX Upgrade
Thank you..
I have Implemented Major upgrade code in my WIX application and it works
fine but iam encountering a strange issue
: Re: [WiX-users] WIX Upgrade
For most of us, if we are not intending to support patching at this time,
"always-major" upgrades are the easiest route, and the easiest way to do
that is to set produ...@id="*". You also have to code the Upgrade element
and determi
For most of us, if we are not intending to support patching at this time,
"always-major" upgrades are the easiest route, and the easiest way to do
that is to set produ...@id="*". You also have to code the Upgrade element
and determine where to sequence RemoveExistingProducts (Hint: if you follow
th
In Wix help file read "How To Guides"\"Updates"\How To: Implement a Major
Upgrade In Your Installer"
-Original Message-
From: Anu Dev [mailto:queryl...@yahoo.com]
Sent: Thursday, September 03, 2009 9:49 AM
To: WIX
Subject: [WiX-users] WIX Upgrade
Hi
Wanted to know if anyone of you
ended
16:03:43: RemoveExistingProducts. Return value 0.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Yu, Brian
Sent: Monday, September 15, 2008 11:49 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WIX Upgrade code
neral discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WIX Upgrade code
Yu, Brian wrote:
> Minimum='2.2.40.499' IncludeMinimum='yes' Maximum='2.2.40.599'
> IncludeMaximum='yes'/>
>
>
> Minimum
Yu, Brian wrote:
> Minimum='2.2.40.499' IncludeMinimum='yes' Maximum='2.2.40.599'
> IncludeMaximum='yes'/>
>
>
> Minimum='2.2.40.599' IncludeMinimum='no' />
>
Major upgrades don't distinguish product versions that differ only in
the fourth place. See
http://msdn.micros
The Directory name should be a 8.3 name, thus the following fixed the errors
Directory LongName is also depricated here (got an error for this), hence
used FileSource attribute.
Thanks
Sathiya
On 10/18/07, Sathiya Priya R <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
>
>
> I'm doing
36 matches
Mail list logo
