Thx Blair, then I'll move the RemoveExistingProducts later in the sequence.
Viv
On 4/28/2010 6:32 PM, Blair wrote:
It happened exactly that way to us. The C++ merge modules seemed to require
the late registration.
-Original Message-
From: Viv Coco [mailto:vcotirl...@hotmail.com
.
-Original Message-
From: Viv coco [mailto:vcotirl...@hotmail.com]
Sent: Friday, March 26, 2010 2:18 AM
To: WiX
Subject: [WiX-users] FileSearch on INSTALLLOCATION, whereas INSTALLLOCATION
is either registry entry or nested Directory tag
Hi,
In the WiX tutorial is a sample
I am attempting to determine if a specific version of a product is already
installed on the system. I basically want to do this to disallow/bail out of
an install if the MSI that is being executed is already installed on the
system.
1) If you run the same msi again you enter the
I got into this problem once when I did the following:
1) Create MyInstaller.msi Version X.X.X
2) Use this installer to install my product
3) Create again the MyInstaller.msi Version X.X.X, meaning a new rebuild
of the msi but with the same version and different Product GUID and
Package GUID as
ok, so I got it right: the 4th field is completely ignored by the
installer, and you have it so that internally the QA knows what version
they are testing.
Thx a lot!
Viv
On 4/13/2010 12:47 AM, Sascha Beaumont wrote:
Because in our environment the fourth version is increased
automatically
Hi all,
I am using the UI InstallDir in the installer of my product:
[code]
Property Id=WIXUI_INSTALLDIR Value=INSTALLDIR /
UIRef Id=WixUI_InstallDir /
UIRef Id=WixUI_ErrorProgressText /
[/code]
For some specific reason we need to get out the license page, so we need
to skip the step where the
Hi Sascha,
Thank you for your answer.
I understood your suggestion, but what it's not clear to me is why do
you actually have the 4th field in the version? I mean the approach you
have would have worked exactly the same also if your version number
would consist of only 3 fields, eg: 2.2.0,
-Original Message-
From: Viv Coco [mailto:vcotirl...@hotmail.com]
Sent: 12 April 2010 08:36
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Remove the license page
Hi all,
I am using the UI InstallDir in the installer of my product:
[code]
Property Id
UPGRADINGPRODUCTCODE is set when you're being uninstalled during an
upgrade, so it sounds like the wrong condition.
Now I get it!!! the UPGRADINGPRODUCTCODE is NOT set when the product is
installed during an upgrade, only when uninstalled during an upgrade. THX!
I think you probably want
Hi all,
I am interested in doing only major upgrades in my installer, this is
why I have in the code for Product and Package the Id=*:
[code]
Product Id=* Name=$(var.ProductName)
Version=$(var.CurrentVersion) Language=1033
Manufacturer=$(var.CompanyName) UpgradeCode=$(var.UpgradeCode)
Package
Hi all,
I would like to run a CA only on the first install. The CA shouldn't be
run on an upgrade. The condition i used is:
(NOT Installed) AND (NOT UPGRADINGPRODUCTCODE)
but it's not working, as the CA is still run on upgrade also.
I found the nice and detailed answer from Blair here:
Wilson
-Original Message-
From: Viv Coco [mailto:vcotirl...@hotmail.com]
Sent: Tuesday, April 06, 2010 1:29 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] First run notepad with my.cfg and only then start
the service
I actually thought about
Hi,
Yes, I used that too, but, at least in my case, the quotes didn't work,
so I had to use it like this:
Condition(NOT UPGRADINGPRODUCTCODE) AND (REMOVE=ALL)/Condition
Viv
On 4/1/2010 9:49 PM, little.forest wrote:
Thanks Sanjay.
This is great. Especially there is a table - much clearer.
'(NOT Installed)
AND (NOT UPGRADINGPRODUCTCODE)/Custom
/InstallExecuteSequence
[/code]
This seems to be doing the job. Is this not correct?
Thx,
Viv
On 4/3/2010 3:20 PM, Bob Arnson wrote:
On 4/1/2010 9:28 AM, Viv Coco wrote:
shown to the user to modify as needed (I give the user the chance
app.
InstallValidate finds no files in use and proceeds to stop services,
uninstall files etc.
3. Custom action to delete the stop monitoring registry item.
Phil Wilson
-Original Message-
From: Viv Coco [mailto:vcotirl...@hotmail.com]
Sent: Wednesday, March 31, 2010 3:34 AM
Hi all,
I install an aaa.ini file together with my binaries. I need a second ini
file (bbb.ini) which is a copy of the first one, it just have a
different name, and it's in the same directory. I was thinking about
using the CopyFile but I need also the following:
1) the CopyFile, meaning the
that template.ini would be on the target machine as aaa.ini
and as bbb.ini which is fine.
But how can I condition the bbb.ini component to be removed only on a
real uninstall - not upgrades, repairs, modifies? Is this doable?
Thx,
Viv
On 4/1/2010 10:43 AM, Viv Coco wrote:
Hi all,
I install
Hi all,
I install along with my application:
1) a service that starts and stops my application as needed
2) a conf file that contains actually the user data and that will be
shown to the user to modify as needed (I give the user the chance to
change it by running notepad.exe with my conf file
down but the process lingers then the process is still there at
file removal time requiring a reboot to delete.
Phil Wilson
-Original Message-
From: Viv Coco [mailto:vcotirl...@hotmail.com]
Sent: Tuesday, March 30, 2010 3:08 AM
To: General discussion for Windows Installer XML toolset
Email Disclaimer
-Original Message-
From: Viv Coco [mailto:vcotirl...@hotmail.com]
Sent: 29 March 2010 11:09
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] don't delete/overwrite a file during major
upgrade
Hi,
Can you install a default
(Unfortunately it's easier said than done and took nearly two major
release cycles for the mindset to catch on here)
Yes, I know, I'm trying to get them understand that. Maybe I'll have
more luck for the next major release.
Thx,
Viv
On 3/30/2010 7:31 AM, Sascha Beaumont wrote:
If you can
Hi,
It's actually a good idea to start with a version lower than I ever
released, so I ended up doing like:
[code]
?define UpgradeCode = GUID?
?define CurrentVersion = 1.0.0?
Upgrade Id=$(var.UpgradeCode)
UpgradeVersion OnlyDetect=no Property=OLDAPPFOUND Minimum=0.0.1
IncludeMinimum=yes
Disclaimer
-Original Message-
From: Viv Coco [mailto:vcotirl...@hotmail.com]
Sent: 30 March 2010 12:12
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Upgrade mechanism
Hi all,
I would like my application to be upgraded if a newer version is run. So
and (NOT UPGRADINGPRODUCTCODE))?
Or the conditioning should be more extensive taking in account that it
should happen only on real uninstall (not installs, not upgrades, not
repairs or modifies)?
Thanks,
Viv
On 3/31/2010 10:42 AM, Viv Coco wrote:
Use a Component Condition on your RemoveFile so
Hi all,
I asked this question as part of another thread and then just noticed
that it was not the right place as that thread was basically about smth
else, so I'll ask this in a new thread here.
I would like a specific file, that it's NOT installed by the installer,
but later created by the
or to reboot the machine on every
upgrade. How can I force the shutting down of the service?
Thx,
Viv ;)
On 3/29/2010 12:21 PM, Viv Coco wrote:
On pre-Vista (pre MSI 4.0) the ServiceControl entries aren't considered
for files-in-use situations. On Restart Manager systems with MSI 4.0 and
above
Hi all,
I would like to schedule the RemoveExistingProducts after
InstallInitialize in my installer:
[code]
RemoveExistingProducts After=InstallInitialize/
[/code]
in order to have first a full uninstall and then an install as my
product it's really small so it's no efficiency issue.
But I
Hi all,
I would like my application to be upgraded if a newer version is run. So
the behaviour should be: if the user tries to install the already
installed version (meaning current version) or an older version, the
installer should bail out with the message current or newer installed.
The
**
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer
-Original Message-
From: Viv Coco [mailto:vcotirl...@hotmail.com]
Sent: 30 March 2010 11:08
To: General
Hi,
Can you install a default configuration file and then copy that to
the user configuration if it doesn't exist?
Well, I could do so, already thought about that, but unfortunately the
application is already in QA so we are not allowed to change anything
to it anymore so everything that is
Thanks guys, helpful tips!
Viv ;)
On 3/29/2010 6:46 AM, Sascha Beaumont wrote:
If this happens again... here's the procedure I usually follow
1) Fix the broken condition.. avoid making any other changes if possible.
2) On a broken machine, recache the MSI with msiexec /fv myproduct.msi
3)
be
unreliable.
Start on install and stop on install? It does both. There is a StopServices
action early in the execute sequence that stops services. Later on (after
files have been installed/replaced) there's a StartServices action.
Phil Wilson
-Original Message-
From: Viv coco
Arghh, yes, thx!
Viv ;)
On 3/26/2010 10:21 AM, ricky sundrani wrote:
Check the spelling INSTALLLOCATION in the value attribute
On Fri, Mar 26, 2010 at 2:45 PM, Viv cocovcotirl...@hotmail.com wrote:
Hi,
I want to save the path where my binaries are installed somewhere in the
Hi,
I read the WiX Tutorial from http://www.tramontana.co.hu/wix/ and there are
some things I didn't understand or couldn't find and as I read that this is the
best place for questions, I'll write them here, but for an easier followup I
will write each question into a separat email. I
Hi,
My installer besides my application installs also a service which is the
babysitter for my application, eg takes care to restart my application if it
crashes. When I want to uninstall everything I get the error message: The
setup must update files or services that cannot be updated
Hi,
I want to save the path where my binaries are installed somewhere in the
registry so I'm doing:
[code]
Directory Id=TARGETDIR Name=SourceDir
Directory Id=ProgramFilesFolder
Directory Id=MyFirstSetup Name=MyFirstSetup
Directory Id=INSTALLLOCATION
Hi,
In the WiX tutorial is a sample that does:
- reads the path to the installation directory from the registry
- checks if in that directory a specific file exists
- if yes, installs the a specific feature (docu)
What I would have wanted would have been:
- reads the path to the
Hi,
Why would one do:
[code]
Directory Id=ProgramMenuFolder Name=PFiles
[/code]
In this specific case (as ProgramMenuFolder is a predefined directory) the
Name doesn't have any means at all right? We could simply do:
[code]
Directory Id=ProgramMenuFolder
[/code]
Is that
Hi,
When I specify for instance the directory where the shortcut should be I also
have to add a component to delete that folder when uninstalling, eg:
[code]
Directory Id=ProgramMenuFolder
Directory Id=ProgramMenuDir Name=MyAppGuiSetupShortcutDir
!--For some
Hi,
If I make a faulty uninstaller and I can't uninstall my product again using the
.msi, how could one do a manual uninstall and cleanup, including hidden issues
that are coming from the .msi file?
I got into this trouble when I added into my installer:
[code]
Condition
40 matches
Mail list logo
