r entry. I know
I'm missing something basic here, but I don't know what.
Sigh
-Original Message-
From: Wilson, Phil [mailto:phil.wil...@invensys.com]
Sent: Tuesday, May 18, 2010 3:41 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Upgrade installation
What you
l Message-
From: Wilson, Phil [mailto:phil.wil...@invensys.com]
Sent: Tuesday, May 18, 2010 3:41 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Upgrade installation
What you're describing is a major upgrade. You didn't mention this, but
Visual Studio setup projects typical
Message-
From: Wix Mailing List [mailto:w...@danhinsley.com]
Sent: Tuesday, May 18, 2010 1:39 PM
To: Wilson, Phil
Subject: RE: [WiX-users] Upgrade installation
Using the .NET Visual Studio Setup Project, I set the UpgradeCode of both
the Install setup project and the Update setup project to be t
le. So it comes down to exactly
what you did and saw in your "upgrade".
Phil Wilson
-Original Message-
From: Wix Mailing List [mailto:w...@danhinsley.com]
Sent: Tuesday, May 18, 2010 12:04 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: R
If you have two separate MSI files then you'll have two entries in
Add/Remove Programs. There's no magic merge that makes them become one
product.
>> But I did the same type of thing using the .NET setup (which produces MSI
files) and it did as I expected. The upgrade recognized that it was the
If you have two separate MSI files then you'll have two entries in Add/Remove
Programs. There's no magic merge that makes them become one product.
Why exactly don't you want to include the file in subsequent updates? If it's a
static file then patches and upgrades won't try to update it anyway
6 matches
Mail list logo
