: Fyodor Koryazhkin [mailto:fyodor...@gmail.com]
Sent: 17 October 2014 08:03
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Wix Upgrade Issue
HI,
I never implemented this my self but try to do the following:
1. Use Minor upgrade instead of Major upgrade. (by definition Major upgrade is
ourceforge.net
> Cc:
> Date: Fri, 17 Oct 2014 10:26:16 +0800
> Subject: [WiX-users] Wix Upgrade Issue
> Hi All,
>
> Here is a scenario that i want to implement.but i don't have good idea to
> implement this.
>
> let's say that someone get a installer and ins
Hi All,
Here is a scenario that i want to implement.but i don't have good idea to
implement this.
let's say that someone get a installer and install it today. tomorrow
someone get a new installer with the higher version number want to install
it on the same PC. the installer with the higher versi
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
, September 29, 2014 12:35 PM
To: 'General discussion about the WiX toolset.'
Subject: [WiX-users] WiX Upgrade Questions
I have an application that was originally installed using a Visual Studio
Installer project. I have authored a WiX replacement with a Major Upgrade
Feature. I have tw
I have an application that was originally installed using a Visual Studio
Installer project. I have authored a WiX replacement with a Major Upgrade
Feature. I have two questions regarding it. When the original application
was installed it allowed the user to choose where to install it. Is it
po
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
& Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
|jocoo...@jackhenry.com
-Original Message-
From: Arvind Janghel [mailto:arvind.jang...@citiustech.com]
Sent: Tuesday, September 16, 2014 6:07 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] WIX : Upgrade Issue
Hi,
I
Hi,
I have implemented major upgrade support in my application installer . As
part of upgrade, there are C# custom actions to backup and restore config
files, and also update the database.
I have scheduled the RemoveExistingProducts after "installinitialize".
However the restore configurat
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
t; appropriate fields in the Upgrade table.
>
> Neil
>
> -Original Message-
> From: Sanjay Rao [mailto:s...@noida.interrasystems.com]
> Sent: 14 January 2011 21:33
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] Wix upgrade proces
- otherwise just set the
appropriate fields in the Upgrade table.
Neil
-Original Message-
From: Sanjay Rao [mailto:s...@noida.interrasystems.com]
Sent: 14 January 2011 21:33
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Wix upgrade process does not consider 4th
a.interrasystems.com]
> Sent: Friday, January 14, 2011 1:33 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] Wix upgrade process does not consider 4th part of the
> version string
>
> Hi,
>
> I have an installer having 4-part version s
y Rao [mailto:s...@noida.interrasystems.com]
Sent: Friday, January 14, 2011 1:33 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Wix upgrade process does not consider 4th part of the
version string
Hi,
I have an installer having 4-part version strings. Our installer stops
installa
Hi,
I have an installer having 4-part version strings. Our installer stops
installation if a newer version is already installed on the system. We
often have alpha/beta releases of our product in which we do not change
first 3 parts of the product. Suppose we have two releases of our product :
R
>> RemoveExistingProducts. Set OnlyDetect to "no" for those properties that
>> contain the packages you intend to remove. Or remove it entirely for those
>> same properties, since it defaults to "no".
>>
>> Leave OnlyDetect set to "yes" fo
quot;yes" for those properties that you won't be
> removing (such as newer versions you use to block installation, etc.)
>
> -Original Message-
> From: Jeremy Rimer [mailto:jeremyri...@gmail.com]
> Sent: Tuesday, July 13, 2010 12:36 PM
> To: General discussion for W
-Original Message-
From: Jeremy Rimer [mailto:jeremyri...@gmail.com]
Sent: Tuesday, July 13, 2010 12:36 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] WIX Upgrade configuration
I've solved my App.Config issues with help from Blair (Thanks, buddy!!!),
but no
I've solved my App.Config issues with help from Blair (Thanks, buddy!!!),
but now I'm running into upgrade path problems...
To set the stage, I have a WIX installer that successfully deploys an
application to it's installation directory, and takes some input from the
user that calls a CA to overwr
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
we have upgrade all the visual studio projects to visual studio 2008
But In Build machine we have visual studio 2005 and Wix 3.0.5419(Wix is
upgrade from Wix3.0.2925). I have not upgraded Visual studio 2008 in build
server. I installed .NET Framework3.5 and compiling all the .net projects.
we ha
[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
A more-or-less clear synopsis with details is here:
http://documentation.installshield.com/robo/projects/installshield12helplib/
MajorMinorSmall.htm
-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
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
Hi
Wanted to know if anyone of you have worked on the following scenario.
1. Application is already installed on the client machine and he wants to
upgrade to a new version.
2. During this process, user is prompted to uninstall prior version and
install the new version.
Rather than p
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
Hi there
I've set up 3 msi. One base install(309) and 2 minor upgrades (499 and
599)
I expect that 599.msi can only br run when 499 is previously patched.
However, I am able to run 599.msi straight after installing 309.msi
How do u specify this range?
309.wxs
4
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
Hello,
I'm doing a wix upgrade from *3.0.3001.0 to 3.0.3412.0* and getting the
following error: Can you please let me know if I'm missing something
obvious?
e:\setup\installers\global\components\webhostingtemplates.wxs(9) : error
LGHT0083 : The file with id 'DefaultPagesFeatureXml' and name '
46 matches
Mail list logo
