Martin,
Package ID should always be different. That's why it is set to '*'. For major
upgrade to work, you need to change product id and version (version in MSI is
first 3 fields. If two versions have the same first 3 fields and differ only
in the fourth field, as far as MSI concerned - they
Me thinks Package Id should also be the same.
In my case I tried to reinstall MSI file by setting the original Product Id
and Version, and keeping Upgrade Code the same. Then I rebuild my wix
project.
However Package Id is set to star (*) and I get the error message below.
If I reuse the same MSI
Hi,
this message is displayed if you try to install a MSI with the same
UpgradeCode and Version but a different ProductCode. So if you want to
see the Repair/Uninstall mode you have to use a msi with the same
ProductCode or maybe event the same msi, which has been used to install
the product.
Hi,
I am using MajorUpgrade element in my wxs.
When I try to install the same version of the MSI, I get the well known
message:
Another version of this product is already installed
[Window Title]
Windows Installer
[Main Instruction]
Another version of this product is already inst
Hi,
Thanks for replying, it works for showing log file on successful installation.
But i also want to show log file on failure/cancel.
Thanks,
Loknath
--
Message: 1
Date: Wed, 22 Jun 2011 10:38:15 +0100
From: Pally Sandher
I simply use this...
.Net Framework 4.0
-Original Message-
From: Sidky Macatangay [mailto:y2k...@gmail.com]
Sent: 22 June 2011 06:21
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Bootstrapping .NET Framework 4.0
I have both .NET Framework 4.0 and Windows Install
I think that the only privilege that you can set in Wix is 'Logonasaservice',
via the user element.
I had to do this by custom action years ago from installshield.
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: 22 June 2011 10:32
To: General discussion fo
You could cover that scenario by checking if USERDOMAIN = COMPUTERNAME.
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotl
Yes, I understand this. Thanks for the heads up. In my environment I think
it will work okay.
On Tue, Jun 21, 2011 at 9:21 PM, Michael Osmond wrote:
> Be carefull using USERDOMAIN, it is the domain of the account that is
> logged in, which is not necessarily that of the domain the machine is in -
To redistribute 3rd party installation packages you will need to use a
bootstrapper. WiX v3.6 has Burn in development which some people are
already using but the other options I can think of off the top of my
head would be dotnetinstaller (http://dotnetinstaller.codeplex.com/) or
SharpSetup (http:/
You could use the optional checkbox on the ExitDialog which would be the
quickest way. See
http://wix.sourceforge.net/manual-wix3/run_program_after_install.htm Instead of
using [#myapplication.exe] in the example give it the full path to your log
file.
Palbinder Sandher
Software Deployment En
http://wix.sourceforge.net/manual-wix3/WixUI_index.htm &
http://neilsleightholm.blogspot.com/2008/08/customised-uis-for-wix.html
both posted many times to this list. I suggest searching in future
before posting.
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 14
No idea. I've never come across giving specific privileges without using
groups. I suspect you'll need a custom action unless anyone else has any
suggestions.
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate
13 matches
Mail list logo
