You can't update a per-machine install from a per-user install (or vice versa).
It's an inherent limitation.
There were some threads on this earlier and you should be able to find them via
search.
From: Chris Lord [chris.l...@atterotech.com]
Sent:
Check your UpgradeCode and Upgrade ID= and make sure they are correct. The
Upgrade ID= should be the UpgradeCode of the product you wish to upgrade. Often
times the UpgradeCode in the new package is also set to the same value. It
basically describes a family of products.
-Original
Innosetup does not use Windows Installer. The bottom line is that Windows
Installer does not support mapped drive setups and Wix only produces Windows
Installer setups.
If you're restricted to use MSI-type setups then other authoring tools will not
help because of the inherent limitation of
I don't see a Tools subfolder under the Test App 1.0 folder you created so
nothing will be installed there.
Not sure why the RemoveFiles doesn't work. Did you get the spelling correct on
the file names?
-Original Message-
From: Arun Perregatturv [mailto:aperregatt...@napcosecurity.com]
/
/Directory
/Directory
I am unsure of how to create Sub Folders.
Yes, File names are correct I don't know why it's unable to Removefile.
Thanks,
Arun Perregattur
-Original Message-
From: Ian Elliott (Excell Data Corporation) [mailto:a-iae...@microsoft.com]
Sent: Wednesday
Folders Install
Thanks I got the sub folders working, now let me try the remove file.
Thanks,
Arun Perregattur
-Original Message-
From: Ian Elliott (Excell Data Corporation) [mailto:a-iae...@microsoft.com]
Sent: Wednesday, December 31, 2008 5:10 PM
To: General discussion for Windows
-Original Message-
From: Ian Elliott (Excell Data Corporation) [mailto:a-iae...@microsoft.com]
Sent: Wednesday, December 31, 2008 5:43 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Wix Sub Folders Install
That's not really an error. It's just pulling test from
to components? I have like at least 100-200
Assemblies, few Services and add another 50-10 files for dependency files and
on top of this Install .NET/SQL.
Thanks,
Arun Perregattur
-Original Message-
From: Ian Elliott (Excell Data Corporation) [mailto:a-iae...@microsoft.com]
Sent
Have you tried the following?
PFXPassword=
-Original Message-
From: Maruti Gouroji (Infosys Technologies Ltd) [mailto:v-mag...@microsoft.com]
Sent: Monday, December 29, 2008 12:47 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Need Help: Importing
I also have a home-made tool for generating components. I have another tool
that generates a complete wix file after you specify directory structure and
files within the directories. It's used to to most of the grunt work and then
the rest is done by hand. (UI based.)
Is there a public share
: Monday, December 29, 2008 1:09 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WIX 3 - Suggestions
How is it different than heat?
-Original Message-
From: Ian Elliott (Excell Data Corporation) [mailto:a-iae...@microsoft.com]
Sent: Monday, December 29
Your analysis appears accurate. It's really not too much work to have a
setup.exe check for the presence of an install. If found then launch with
proper command line for minor upgrade else just do normal launch.
You can find sample code to peruse at www.devage.com in the dotNetInstaller
You say that it doesn't seem to run the CAs. Have you checked a verbose log
file to see for sure?
-Original Message-
From: David Bartmess [mailto:david.bartm...@wallst.com]
Sent: Friday, December 19, 2008 1:03 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re:
Changing the GUIDs should do the trick. That way, they will be individually ref
counted. However, you need to be sure that the key paths are unique and I'm not
exactly sure what constitutes the key paths for such items.
Best bet is to test it and see what happens.
-Original Message-
in the log
-Original Message-
From: Ian Elliott (Excell Data Corporation)
[mailto:a-iae...@microsoft.com]
Sent: Friday, December 19, 2008 2:07 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Repair mode doesn't run custom actions
You say that it doesn't
.
Subject: Re: [WiX-users] Repair mode doesn't run custom actions
They're scheduled in the InstallExecuteSequence.
-Original Message-
From: Ian Elliott (Excell Data Corporation)
[mailto:a-iae...@microsoft.com]
Sent: Friday, December 19, 2008 3:39 PM
To: General discussion for Windows Installer
I'm not aware of any method other than command line or exe file. That is the
official guidance from Microsoft.
http://msdn.microsoft.com/en-us/library/aa367574(VS.85).aspx
-Original Message-
From: Martin Lierschof [mailto:mliersc...@vizrt.com]
Sent: Tuesday, December 16, 2008 1:23 AM
updating.
I am not sure but since I start reading the documents for wix/msi and I did
read them, I could not find an execution order or something for msiexec.
Sorry for the long story but this story don't fit for me.
Regards
Martin Lierschof
-Ursprüngliche Nachricht-
Von: Ian Elliott (Excell
https://lists.sourceforge.net/lists/listinfo/wix-users
-Original Message-
From: Sangeetha Haudakari (Excell Data Corporation)
[mailto:a-san...@microsoft.com]
Sent: Tuesday, December 16, 2008 1:27 PM
To: WiX-users@lists.sourceforge.net
Subject: [WiX-users] How to unsubscribe from this
Are the files in question assemblies being installed to the GAC?
Also, why are you lowering the version of the files?
-Original Message-
From: Sudripta Nandy (Sarangsoft Corporation) [mailto:v-su...@microsoft.com]
Sent: Friday, December 12, 2008 12:30 PM
To:
Since Sudripta is in-house, I contacted her and took a look at the msi's. There
are some component rule violations happening here. :)
-Original Message-
From: Wilson, Phil [mailto:phil.wil...@wonderware.com]
Sent: Friday, December 12, 2008 3:02 PM
To: General discussion for Windows
.
Thanks
Prasoon
Ian Elliott (Excell Data Corporation) wrote:
Your log snippet shows that the component is to be installed. If the
script did not run (and it's correctly associated with that component)
then it is hard to tell why from what you have posted. It would be better
to put the entire
, Ian Elliott (Excell Data Corporation)
[EMAIL PROTECTED] wrote:
What is the full path to the log file?
-Original Message-
From: prasoon81 [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 03, 2008 9:41 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Problem regarding
I think you are stuck with the dialog option. Per-user can only uninstall that
user, and per-machine can only uninstall per-machine, AFAIK.
-Original Message-
From: Colin Bleckner [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 03, 2008 1:38 PM
To: General discussion for Windows
As long as the previous version have an UpgradeCode guid then just author the
different guids in the Upgrade table of the new msi's and follow the rules for
authoring major upgrades.
http://blogs.technet.com/alexshev/archive/2008/02/15/from-msi-to-wix-part-8-major-upgrade.aspx
-Original
Just Google wix remove user and the first hit shows you how to do it.
-Original Message-
From: Vuchuru, Surekha (SBT US EXT) [mailto:[EMAIL PROTECTED]
Sent: Friday, November 07, 2008 10:00 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Modifying a
Do you have logic in your install that blocks if a newer version is found?
You will need a new Upgrade entry to detect prior versions that have the new
upgrade code, too. (The one you are calling CurUpgradeID.)
-Original Message-
From: Colin Bleckner [mailto:[EMAIL PROTECTED]
Sent:
to get a way for extensions to recommend their
resources as KeyPaths. Ian, would you open a bug against candle.exe so we
don't lose this. Probably should fix this before locking down WiX v3
completely.
-Original Message-
From: Ian Elliott (Excell Data Corporation) [mailto:[EMAIL PROTECTED
If I'm reading this correctly you are trying to launch an exe (which the
program installed) before InstallFinalize. I'm not sure if that will work.
The recommended way is to launch at the very end using an immediate custom
action.
-Original Message-
From: Wilson, Phil [mailto:[EMAIL
Hi,
I've been tasked with the following:
1.)Create a new group
2.)Add permissions to the new group on a registry key
I couldn't find a way to create a new group via wix so ended up using a custom
action which calls net.exe.
I'm having trouble trying to use PermissionsEx to set
] registry permissions on new groups
Ian Elliott (Excell Data Corporation) wrote:
I'm having trouble trying to use PermissionsEx to set permissions for the new
group. Is this possible or does it only allow setting permissions for
standard groups such as Network Service, Administrators, etc
, 2008 11:34 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] registry permissions on new groups
Ian Elliott (Excell Data Corporation) wrote:
I'm having trouble trying to use PermissionsEx to set permissions for the new
group. Is this possible or does it only
I've been asked to create a virtual directory that points to a network path. It
appears from the help file that I must refer to a Directory element when
defining the WebVirtualDir element.
Is there some other way to accomplish this short of writing a custom action?
A condition of NOT REMOVE will run during both install and repair.
-Original Message-
From: Eric Maines [mailto:[EMAIL PROTECTED]
Sent: Monday, November 03, 2008 2:04 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] CustomAction after Install or Repair?
Hi, I have a
Bob,
You mentioned in your original mail that you were trying a major upgrade. A
major upgrade does not use the REINSTALL and REINSTALLMODE parameters.
The tutorial is actually correct when it says to change the package GUID for
major upgrade. You should assign a package GUID for every new msi
Have you searched through the Wix help file using keywords like registry and
permissions?
-Original Message-
From: Sandeep Gautam (HCL Technologies Ltd) [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 30, 2008 11:03 AM
To: General discussion for Windows Installer XML toolset.
Subject:
Hi,
We've recently seen the following error sometimes in builds. When we retry the
build leg, the error disappears.
We've caught the error on different build machines with different products
where 3.0/2.0 wix are used.
Product with 3.0 wix:
1errors in directory
Elliott (Excell Data Corporation) [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 28, 2008 08:49
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] error LGHT0217 - The Windows Installer Service could not
be accessed
Hi,
We've recently seen the following error sometimes in builds. When we
This is more of a windows installer question. Please see the following:
http://msdn.microsoft.com/en-us/library/aa368010.aspx
-Original Message-
From: Andrew Kendall [mailto:[EMAIL PROTECTED]
Sent: Monday, October 27, 2008 10:13 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users]
This should get you started:
http://blogs.technet.com/alexshev/archive/2008/02/15/from-msi-to-wix-part-8-major-upgrade.aspx
Also, when a major upgrade runs the UPGRADINGPRODUCTCODE property is passed
into the version being uninstalled.
-Original Message-
From: chaiguy1337 [mailto:[EMAIL
I've used a custom action to do something similar in the past. A stripped down
version of the code is below. I can't guarantee 100% effectiveness but it
worked for my needs at the time.
UINT __stdcall FunctionName (MSIHANDLE hMsi)
{
UINT uiStatus = ERROR_SUCCESS;
WriteToLog( hMsi,
profiles is tricky from what I've heard.
-Original Message-
From: Ian Elliott (Excell Data Corporation) [mailto:[EMAIL PROTECTED]
Sent: Friday, October 24, 2008 10:41
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] uninstall per user product
I've used
removed (which I
assume is the case in an explicit uninstall), which makes sense. Is this
correct?
Ian Elliott (Excell Data Corporation) wrote:
This should get you started:
http://blogs.technet.com/alexshev/archive/2008/02/15/from-msi-to-wix-part-8-major-upgrade.aspx
Also, when a major upgrade
It sounds like the two msi's don't have ALLUSERS set to the same value. I don't
believe you can perform a major upgrade on msi's that don't match. They both
have to be per-user or per-machine. You can't mix and match as far as major
upgrades go.
-Original Message-
From: chaiguy1337
http://msdn.microsoft.com/en-us/library/aa370536(VS.85).aspx
From: Sandeep Gautam (HCL Technologies Ltd) [EMAIL PROTECTED]
Sent: Friday, October 24, 2008 6:51 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] How to enable
Here is code from an installer I have that works for me:
Component Id=CID_Logs Guid={837A1B74-98C9-4042-B51D-58F38448CE46}
Location=local DiskId=1
CreateFolder
Permission GenericAll=yes User=Administrators /
Permission GenericRead=yes GenericWrite=yes User=Network Service /
/CreateFolder
If you don't want the original msi to execute the custom action when being
uninstalled via major upgrade, you need the condition of NOT
UPGRADINGPRODUCTCODE to be in the original msi. It's not clear to me if you
have that condition in the original msi or the second msi.
-Original
I don't think Wix has a native way to get the version number. However, using
the Upgrade table, if you define a row for each version you are trying to
detect, then if the property of that row has the GUID then you know that
version exists.
Also, you can use the api MsiGetProductInfo in a
What conditions have you tried on the component? Have you tried NOT Installed?
Are you creating the database with SqlDatabase tag? If so, please paste your
code for that tag.
-Original Message-
From: Sandeep Gautam (HCL Technologies Ltd) [mailto:[EMAIL PROTECTED]
Sent: Thursday,
You should be able to Google msi chainer or msi bootstrapper (or something
similar) and find some information.
There is one free chainer that I have used in the past and that works well
located at:
http://www.codeproject.com/KB/install/dotNetInstaller.aspx
You can download the source and see
Also, I believe properties cannot begin with numbers so the following
properties are illegal:
O2003PIAINSTALLED
O2007PIAINSTALLED
-Original Message-
From: David Bartmess [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 14, 2008 8:29 AM
To: wix-users@lists.sourceforge.net
Subject:
There is good info on major upgrades here:
http://blogs.technet.com/alexshev/archive/2008/02/15/from-msi-to-wix-part-8-major-upgrade.aspx
There is a section called How upgrade works that should help you out.
If I understand you correctly when you install the upgrade, the original
product is
with the letter O... but it
is tough to see with that font, but there is a slight difference (the
letter O is more round and the number 0 is more oval).
Jim Williams
-Original Message-
From: Ian Elliott (Excell Data Corporation)
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 14, 2008 10:24
Hi,
I haven't yet used Wix fragments but have used a couple of include commands.
I've been trying to research what the difference is between using fragments vs
including code via ?include file.wxs ? type tags but am not finding anything.
Can anyone offer a basic explanation on how the two
library rather than actual source
code. For in-house development this is a better alternative to merge modules.
-Original Message-
From: Ian Elliott (Excell Data Corporation) [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 14, 2008 11:04 AM
To: General discussion for Windows Installer XML
8:34 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How Update / Upgrade strategy (small, minor,
major) affect file overriding?
That was it - I needed to change the file version and now everything works
ok. Thx for all the help!
Ian Elliott (Excell Data Corporation) wrote
it at the moment, but I think we should be ok using a
wildcard. The only other thing that I can think of at the moment is having the
build process generate the guid, but I'm avoiding that for the moment.
Thanks for the advice.
Adam
-Original Message-
From: Ian Elliott (Excell Data Corporation
I agree that you should make two simple installers and try it out.
However, I don't think it will work. Once you install package A and then try to
install package B, it will likely put you into maintenance mode. (Since you're
using the same product code.)
-Original Message-
From:
I got the feeling he wanted to have the two installers somehow be the same
product because he was asking about features. What you say is true as it's easy
to do with two separate product codes and using shared components.
Ian
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL
@lists.sourceforge.net
Subject: Re: [WiX-users] How Update / Upgrade strategy (small, minor, major)
affect file overriding?
Ian Elliott (Excell Data Corporation) wrote:
Your command line looks wrong:
msiexec /i ExampleInstaller.msi REINSTALALL=ALL REINSTALLMODE=vomus
should be
msiexec /i
There is one side effect that I can think of (and have experienced) during
daily development. Say your build version number changes once per day.
Everything will work fine if you only attempt to install today's version over
yesterday's version.
Now, if you are developing and build multiple
If you specify the property name with lower case letters then it is no longer a
public property and can't be passed in via command line. I assume you are
passing these values in so that might explain what is going on.
There is some good info here on properties:
, October 08, 2008 3:39 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How Update / Upgrade strategy (small, minor, major)
affect file overriding?
Thx for the answer
Ian Elliott (Excell Data Corporation) wrote:
For the minor upgrade and small update you don't make use of the Update
If you use the Upgrade tag, you are doing a major upgrade. In this case, the
old version is removed and the new version is installed. If the files change
between the versions then you will get the latest versions after the upgrade.
Setting the OnlyDetect parameter to yes means that you just
Seems like someone answered this one earlier. You have spelled your property
two different ways in different locations:
INSTALLLSFILES
INSTALLPSFILES
-Original Message-
From: Sandeep Gautam (HCL Technologies Ltd) [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 07, 2008 3:59 PM
To:
=INSTALLPSFILES Value=11/Publish
But my component is not executing.
If I will assign value like :
Property Id= INSTALLPSFILES value =1
Then my component is executing.
-Original Message-
From: Ian Elliott (Excell Data Corporation) [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 07
with 3.0.4513.0, but we're seeing the same install errors as you are with
the latest build.
On Tue, Sep 30, 2008 at 12:56 PM, Ian Elliott (Excell Data Corporation)
[EMAIL PROTECTED] wrote:
I finally convinced my team to upgrade to Wix 3 and now our certificate
installer is failing:
MSI (s) (C4
I finally convinced my team to upgrade to Wix 3 and now our certificate
installer is failing:
MSI (s) (C4:08) [15:50:50:560]: Invoking remote custom action. DLL:
C:\WINNT\Installer\MSI13A.tmp, Entrypoint: InstallCertificates
InstallCertificates: Error 0x80070057: Failed to open PFX file.
You should have a look at the msi help on the types of upgrades at
http://msdn.microsoft.com/en-us/library/aa370579(VS.85).aspx. What you are
experiencing is normal behavior unless you specifically author for upgrading.
There is also good information on one of the upgrade types (major upgrade)
I have some sql scripts that should only be run on initial install and never
again. Unfortunately, before this was released, the scripts were in such a
state such that they couldn't detect that they had already been run. So, when
the component installs during the major upgrade the scripts run
I finally convinced my team to upgrade to Wix 3 and now our certificate
installer is failing:
MSI (s) (C4:08) [15:50:50:560]: Invoking remote custom action. DLL:
C:\WINNT\Installer\MSI13A.tmp, Entrypoint: InstallCertificates
InstallCertificates: Error 0x80070057: Failed to open PFX file.
?
-Original Message-
From: Ian Elliott (Excell Data Corporation) [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 30, 2008 09:56
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] failed certificate install
I finally convinced my team to upgrade to Wix 3 and now our certificate
installer
72 matches
Mail list logo
