Hi,
Am 17.02.2011 02:07, schrieb Bob Arnson:
On 16-Feb-11 17:13, Lukas Haase wrote:
However, what happens when program with same UpgradeCode is first
installed globally as administrator and the next version installed as
non-admin user?
MSI doesn't support a per-machine package upgrading
Hi,
How is it handled when I do not check for admin rights and users install
my program without admin privileges?
In this case, they won't be able to register the program in the global
Uninstall list/MSI registry I guess.
However, what happens when program with same UpgradeCode is first
Hi,
It was mentioned a few times on this list that if the UpgradeCode stays
the same, MSI performes an upgrade.
This is my preamble:
Wix xmlns='http://schemas.microsoft.com/wix/2006/wi'
Product Name='Test' Id='*' UpgradeCode='$(var.UpgradeCode)'
Language='1031' Codepage='1252'
://neilsleightholm.blogspot.com/2009/01/wix-script-for-major-upgrade
s.html
Neil
-Original Message-
From: Lukas Haase [mailto:lukasha...@gmx.at]
Sent: 03 August 2010 12:01
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Update Detection
Hi,
It was mentioned a few times
Hi,
I looked at the docs at
http://msdn.microsoft.com/en-us/library/aa368250%28VS.85%29.aspx but I
could not find any information:
Within a DLL extension for MSI, how can I found out ...
a) In which UI mode I am (full, reduced, simple, no)
b) If I am called in InstallUISequence or
Haase [mailto:lukasha...@gmx.at]
Sent: Monday, July 26, 2010 3:56 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Does the msi-filename matter?
Dear Bob,
Am 25.07.2010 15:45, schrieb Bob Arnson:
On 7/25/2010 8:10 AM, Lukas Haase wrote:
However, there is also need to replace
Hi,
As written in some other posts I have written A DLL for MSI which
detects my old setup program, asks the user if he wants to deinstall and
deinstalls the old product.
However, the old setup application does not offer a silent uninstall.
Right now, I call the DLL after LaunchConditions in
, since WI can only deal with MSI packages, and you will
need to execute the uninstall executable somehow/somewhere.
-Original Message-
From: Lukas Haase [mailto:lukasha...@gmx.at]
Sent: Sunday, July 25, 2010 5:18 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users
?id=42). It was pretty hard overall and
took more effort to clean-up once the customers were off those very old
versions.
dB. @ dblock.org
Moscow|Geneva|Seattle|New York
-Original Message-
From: Lukas Haase [mailto:lukasha...@gmx.at]
Sent: Wednesday, July 21, 2010 4:20 PM
Dear Bob,
Am 25.07.2010 15:45, schrieb Bob Arnson:
On 7/25/2010 8:10 AM, Lukas Haase wrote:
However, there is also need to replace Product/@Id and
Product/@UpgradeCode ...
Use preprocessor variables and/or localization variables.
Thank you for your reply. This is what I already did
will have that double-check running.
-Original Message-
From: Lukas Haase [mailto:lukasha...@gmx.at]
Sent: Sunday, July 25, 2010 5:01 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Is tutorial sample CA broken? (was: Re:
InstallExecuteSequence completely ignored)
Hi all,
I
for an installation :)
!ERROR_SUCCESS isnt a valid custom action return. See this list
http://msdn.microsoft.com/en-us/library/aa368072%28VS.85%29.aspx
-Original Message-
From: Lukas Haase [mailto:lukasha...@gmx.at]
Sent: 26 July 2010 11:44
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users
] http://www.tramontana.co.hu/wix/lesson3.php#3.1
[2]
http://www.tramontana.co.hu/wix/download.php?file=samples/sampleca.ziptype=application/zip
Am 23.07.2010 14:18, schrieb Lukas Haase:
Dear Pally,
Am 23.07.2010 11:04, schrieb Pally Sandher:
MSI (c) (74:80) [21:07:26:477]: Doing action
Dear Rob,
Thank you for your reply.
Am 23.07.2010 08:01, schrieb Rob Mensching:
1. You can have multiple .wxs files to create a single or set of MSI files.
I recommend breaking your product down into useful chunks and putting them
in Fragments then grouping the Fragments in logical files.
(and the only
supported way if you must do so from the execute sequence) is using the
MsiProcessMessage API (or something that wraps it, like WcaProcessMessage or
Microsoft.Deployment.WindowsInstaller.Session.Message).
-Original Message-
From: Lukas Haase [mailto:lukasha...@gmx.at]
Sent
Dear Rob,
This was also my first guess. But I deleted and recompiled a few times.
I even renamed the file.
I do not know which entry in the logfile you mean but the one line
containing cache on the top is:
MSI (c) (04:E8) [13:50:57:178]: Resetting cached policy values
Another two lines
Dear Pally,
Am 23.07.2010 11:04, schrieb Pally Sandher:
MSI (c) (74:80) [21:07:26:477]: Doing action: ValidateProductID Aktion
21:07:26: ValidateProductID.
That's the InstallUISequence not the InstallExecuteSequence.
Indeed! I changed now to InstallUISequence and now it works!
But why? The
://wix.sourceforge.net/manual-wix3/heat.htm
-Original Message-
From: Lukas Haase [mailto:lukasha...@gmx.at]
Sent: Wednesday, July 21, 2010 3:17 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Automatically include arbitrary files
Am 22.07.2010 00:07, schrieb Lukas Haase
Hi,
As proposed in one mail I wrote a DLL for detecting old installations.
But WiX seems to completely ignore InstallExecuteSequence!
I played around, tried different things but it is just ignored!
For testing I just added this to my file:
Property Id='NOTEPAD'Notepad.exe/Property
for it (just test every conceivable
scenario before letting anything out the door). Of course, the savings using
patching goes up the more you don't change, so my back-of-the-envelope
analysis may not be correct.
Blair
-Original Message-
From: Lukas Haase [mailto:lukasha...@gmx.at]
Sent
Thank you everybody for the discussion!
The result is clear to me: I won't use minor- and small updates.
One question concerning Best practice left for the deployment.
In fact my application consists of:
- Viewer (EXE, DLL, CHM)
- Database (dat-file (80MB), bunch of PDFs)
- License1.RTF,
Dear Blair,
Am 22.07.2010 01:04, schrieb Blair:
1. You can build MSIs with WiX that don't require running the setup as
administrator. Nothing that can be done outside of Windows Installer without
elevation requires elevation in Windows Installer to also do.
In fact this is exactly what I do
Hi,
Today I began creating my first WiX project. Until now I used
SetupSpecialist but as I am facing serious problems with it I want to
use WiX in future.
This is my first big question: On clients' computers there will be an
old instance of my program (with SetupSpecialist) installed. Even
Hi,
My setup project consists of a bunch of static files (application,
DLL), a huge databasefile and a vast amount of PDF files. The PDF files
are very volatile, they change from update to update (some are removed,
some are added but no of them are changed).
As they are many files I would
Dear Pally,
I have the same problem. BIG HINT for all users!
When you get
heat.exe : warning HEAT5150 : Could not harvest data from a file that
was expected to be a SelfReg
DLL: TestProtocol.dll. If this file does not support SelfReg you can
ignore this warning. Otherwise, this error detail
Hi,
Does the filename of the msi file matter in any way?
I really DO NOT hope so! Because I have no influence if the user renames
the file before installing?!
[1] says: There are cases when the Windows Installer forces you to use
a major upgrade [...] You have to when you change the name of
setup a component group for your PDF
files (then you can simply refer to them from your feature using the
ComponentGroupRef element).
-Original Message-
From: Lukas Haase [mailto:lukasha...@gmx.at]
Sent: Wednesday, July 21, 2010 1:29 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX
Am 22.07.2010 00:07, schrieb Lukas Haase:
Dear Blair,
I do not fully understand. You mean the -ag switch?
But then on every compile the PDF files get a different GUID, don't
they? Then back to the original question: Does it matter in ANY way if
they get a different GUID on upgrades?
I.e
Dear Blair, Dear Christopher,
Thank you for your reply.
Am 22.07.2010 00:11, schrieb Blair:
[...]
This is part of the reason huge numbers of software producers distributing
over the internet use self-extract-and-launch-style wrappers (zip-exe style)
for their MSI distribution.
Do you have a
29 matches
Mail list logo
