.'
Subject: Re: [WiX-users] Minor upgrade
Yeah...iam maintaing command line like.
msiexec -I $(.msi) REINSTALL=ALL REINSTALLMODE=vomus but it's not working.
Is it mandatory to maintain property tag like
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
S
ssion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Minor upgrade
Are you using the correct command line to install it ?
http://msdn.microsoft.com/en-us/library/windows/desktop/aa367575%28v=vs.85%2
9
.aspx
-Original Message-
From: Chaitanya [mailto:chaita...@pointcross.com]
Sen
Are you using the correct command line to install it ?
http://msdn.microsoft.com/en-us/library/windows/desktop/aa367575%28v=vs.85%29
.aspx
-Original Message-
From: Chaitanya [mailto:chaita...@pointcross.com]
Sent: 30 October 2012 05:59
To: WiX-users@lists.sourceforge.net
Subject: [WiX-us
ribing what WIX needs to build a MSI.
>
>
> -Original Message-
> From: Aseem Chiplonkar [mailto:asc...@gmail.com]
> Sent: Monday, June 18, 2012 11:34 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Minor upgrade or Patch creating using
t: Monday, June 18, 2012 11:34 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Minor upgrade or Patch creating using Visual Studio
2010
Hi,
Thanks for your pointers.
What I am confused with is that the code shown to create the Patch.wxs does not
contain the
Hi,
Thanks for your pointers.
What I am confused with is that the code shown to create the Patch.wxs does
not contain the product code or upgrade code at all
http://schemas.microsoft.com/wix/2006/wi";>
http://www.dynamocorp.com/";
DisplayName="Sample Patch"
Description="
1. Create your first version of the MSI in VS.
2. Create a second version of the MSI in VS as a new project that implements
a minor upgrade (see MSDN if you need any help with that - basically change
the version number, but not the product or upgrade codes, and obey the
component rules).
3. The nex
On 05-Jan-12 16:33, Hoover, Jacob wrote:
>Is there a way of informing an end user that a patch is not valid (due
> to a newer patch all ready being applied)?
Check patch applicability. That's what Burn does. The 1.0.2 MSP won't be
applicable to a 1.0.3 product.
--
sig://boB
http://joyofsetu
Patches by definition are always repairs. They are either "small updates" or
"minor upgrades", run as if recaching had been enabled from the
corresponding MSI.
-Original Message-
From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Sent: Thursday, January 05, 2012 1:34 PM
To: General d
Ok, thanks all for clarifying anyway. cheers.
_
http://clk.atdmt.com/UKM/go/195013117/direct/01/
--
ThinkGeek and
the environment before printing this e-mail
> -Original Message-
> From: Pally Sandher [mailto:pally.sand...@iesve.com]
> Sent: Monday, June 07, 2010 5:46 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] minor upgrade and RemoveE
The answer would be no. Changing the Product Code means it's not a Minor
Upgrade, it's a Major Upgrade. See ->
http://msdn.microsoft.com/en-us/library/aa370579.aspx
You could deploy the changes as an MSP rather than an MSI.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141
On 6/7/2010 8:10 AM, warne warne wrote:
> Hi, is it any way possible possible to do a minor upgrade and automatically
> remove related products in the background?
No, that's a major upgrade.
> The scenario is I made some bug fixes to our product that dont seem to
> warrant a major upgrade. My v
On 15/03/2010 23:21, Michael Osmond wrote:
> That is correct for a minor upgrade. You keep the UpgradeCode and
> ProductCode the same, and the PackageCode and Version must change (see the
> MSI SDK for details). FindRelatedProducts is not used for a minor upgrade.
OK, understood. I'll email t
Hi John
That is correct for a minor upgrade. You keep the UpgradeCode and ProductCode
the same, and the PackageCode and Version must change (see the MSI SDK for
details). FindRelatedProducts is not used for a minor upgrade.
Also be aware when you start an MSI with a minor upgrade it is act
for launching your readme pdf file. Be sure to replace
OLDPRODUCT with your actual property's name to use my fix.
-Original Message-
From: Giora keinan [mailto:grkei...@gmail.com]
Sent: Monday, January 18, 2010 1:15 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [
the
REINSTALL or the Installed properties.
-Original Message-
From: CP YEH [mailto:ntde...@gmail.com]
Sent: Monday, January 18, 2010 12:46 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] minor upgrade - how to check installed program
version?
Thank you
to:grkei...@gmail.com]
> Sent: Monday, January 18, 2010 6:15 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Minor Upgrade and original msi file name.
>
> Hello
> Thanks for the quick answer.
>
> I have two quick questions:
> 1. My
Sent: Monday, January 18, 2010 11:55 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] minor upgrade - how to check installed program
> version?
>
> Thank you very much for your reply.
> My msi is pretty small in that it contains only few executabl
YEH [mailto:ntde...@gmail.com]
Sent: Monday, January 18, 2010 11:55 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] minor upgrade - how to check installed program
version?
Thank you very much for your reply.
My msi is pretty small in that it contains only few ex
Thank you very much for your reply.
My msi is pretty small in that it contains only few executable
files(exe/dll). Every now and then there are changes to these files so
I need to provide updates so that the user can download the upgrade
packages to upgrade their application. It's also possible tha
Normally those are checked by your bootstrapper that sets the REINSTALL and
REINSTALLMODE values on the commandline. If your bootstrapper doesn't check
versions you will need to write that yourself.
Question: What use case do you have for using minor upgrades? Is it for
supporting patching?
-
is:
-Original Message-
From: Giora keinan [mailto:grkei...@gmail.com]
Sent: Monday, January 18, 2010 6:15 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Minor Upgrade and original msi file name.
Hello
Thanks for the quick answer.
I have two
Hello
Thanks for the quick answer.
I have two quick questions:
1. My understanding is that if I want to do minor upgrade after a major
upgrade I should use the Major upgrade product id instead of the
original installation product id.
2. Is there a way to do an ifdef in the wxs file. I want to u
On 1/17/2010 11:10 AM, Giora keinan wrote:
> I have a problem in minor update. In minor upgrade the msiexec is
> looking for the upgrade name, which should be the same as the original
> msi name.
> The problem is that sometimes the original setup filename is modified
> during download. For example
Some questions.
What is your REINSTALLMODE value?
The files that are not replace: are they binary files with version
resources, or not? If not (such as text or xml) have they been modified in
any way?
You mention adding new files. These files were added to already existing
components? Did you chang
Sonar,
Have you looked at the sample on Alex's blog for doing major upgrades? The
details are at
http://blogs.technet.com/alexshev/archive/2008/02/15/from-msi-to-wix-part-8-major-upgrade.aspx.
It's a little lengthy but it should give you the details you need to make this
work properly.
Neil
I just realised that in fact, I want to do major upgrade.
I suppose that means uninstalling in the background (but with few files left
untouched), stopping/reinstalling some services and running sql scripts.
So, all previous changes and approach stays, just need to add different
product Id ?
--
Hi Rob, Thanks for the help.
Rob Hamflett wrote:
>
> The Upgrade table only comes into play when doing a major upgrade. A
> minor upgrade is basically a
> repair with a new set of files.
>
> Rob
>
--
View this message in context:
http://www.nabble.com/Minor-upgrade-issue-revisited-tp1488
The Upgrade table only comes into play when doing a major upgrade. A minor
upgrade is basically a
repair with a new set of files.
Rob
Nicholls, Rob (CSS) wrote:
> Hi all,
>
> Sorry for the horrible formatting - here goes again!
> I am new here but have searched the list and cannot find a rele
Ali-Akber Saifee wrote:
> So does this mean that in the case of drastic upgrading - component
> removal etc - would it be a better idea to completely remove the
> product under upgrade and then install?
That's the realm of major upgrades. See the MSI SDK doc on the types of
upgrades that are av
Hey,
Thanks.
So does this mean that in the case of drastic upgrading - component
removal etc - would it be a better idea to completely remove the
product under upgrade and then install?
./Ali
On Dec 12, 2007, at 12:45 PM, Bob Arnson wrote:
> Ali-Akber Saifee wrote:
>> * everything is kept th
Ali-Akber Saifee wrote:
> * everything is kept the same except the version and the package code.
> * the second package contains new binaries, but actually has a few
> components removed, and some custom actions removed.
>
> upon running the second installer in upgrade mode (msiexec /fvomus
> P
Properties are case-sensitive, so try REINSTALL in your condition.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Craig Ward
Sent: Tuesday, August 28, 2007 8:35 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] minor upgrade: r
Brent B. Powers wrote:
> I'm having issues with upgrades, so I converted the tramontina tutorial
> SampleUpgrade to Wix3. Installing the first (old) package is fine.
> Removing old and installing new is fine. However, when I install the
> old, and then attempt a minor upgrade via msiexec ... RE
On 1/25/07, Chris Allen <[EMAIL PROTECTED]> wrote:
>
> Johan Appelgren wrote:
> > I've created a setup package using Wix 3.0.2420.0 that I've used to
> > install our product on a computer from a CD (removable media). But
> > when I try to perform a minor upgrade it prompts me for a disk,
> > "Pleas
Johan Appelgren wrote:
> I've created a setup package using Wix 3.0.2420.0 that I've used to
> install our product on a computer from a CD (removable media). But
> when I try to perform a minor upgrade it prompts me for a disk,
> "Please insert disk".
>
> In the logs there is a PackageMediaPath p
The log file should tell you what caused the prompt for source. Start there,
then work back.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Johan Appelgren
Sent: Wednesday, January 24, 2007 2:04 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users
, 2007 12:30 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] minor upgrade not upgrading all files
The recipe for a minor upgrade by reinstalling the product is to rebuild
the MSI file with the higher versioned code files, change its
PackageCode, increment its ProductVersion, and
The recipe for a minor upgrade by reinstalling the product is to rebuild
the MSI file with the higher versioned code files, change its
PackageCode, increment its ProductVersion, and install with msiexec /I
REINSTALL=ALL REINSTALLMODE=vomus. If you broke the rule
"don't delete a component" that's s
40 matches
Mail list logo
