Is it possible that you need to specify a Minimum value for OLDERFOUND?
Jim Williams
On Dec 7, 2010, at 3:21 AM, Theo Landman wrote:
> Hello,
> I'm trying to debug why a I cannot get WiX 3.0 to remove my older MSI
> installation created with InstallShield. I have the following W
It looks like you are trying to link (light) WiX source files.
Shouldn't you be using 'candle' to compile them first
Jim Williams
On Apr 30, 2010, at 10:18 AM, wallywojo wrote:
>
> I searched and found a few matches with no replies. Can anyone
> assist when
&g
Do you have a RemoveExistingProducts action defined in your execution sequence?
Jim Williams
-Original Message-
From: Sudripta Nandy (Sarangsoft Corporation) [mailto:v-su...@microsoft.com]
Sent: Wednesday, April 01, 2009 4:03 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users
completely ended and released the folder.
Can you move your CA earlier in the sequence before RemoveFiles to try and
alleviate the problem?
Jim Williams
-Original Message-
From: Adam Langley [mailto:alang...@winscribe.com]
Sent: Tuesday, March 17, 2009 1:16 PM
To: General discussion for W
Is your custom action synchronous or asynchronous? If asynchronous, perhaps
your custom action isn't finishing in time before the attempt to delete the
folders is done.
Jim Williams
-Original Message-
From: Adam Langley [mailto:alang...@winscribe.com]
Sent: Monday, March 16, 2009
main
installer.
Jim Williams
-Original Message-
From: MacDiarmid, James D [mailto:james.macdiar...@eds.com]
Sent: Friday, February 20, 2009 11:01 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Files in an MSI
Actual I was thinking more along the lin
You could try an administrative install:
msiexec /a xxx.msi
Jim Williams
-Original Message-
From: MacDiarmid, James D [mailto:james.macdiar...@eds.com]
Sent: Friday, February 20, 2009 9:05 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Files
deployment
projects.
Jim Williams
-Original Message-
From: Colin Fox [mailto:greenene...@gmail.com]
Sent: Tuesday, December 23, 2008 10:15 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install location based on registry key
On Mon, Dec 22, 2008 at 11:
Fixing the formatting:
Jim Williams
425-221-0289 m
-Original Message-
From: Jim Williams [mailto:jimwilliam...@comcast.net]
Sent: Monday, December 22, 2008 11:35 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Install loca
To make it a little clearer, you can sequence it before LaunchConditions so
it will be done near the beginning of the installation process:
Now, about that million billion dollars... :-)
Jim Williams
-Original Message-
From: Jim Williams [mailto:jimwilliam...@comcast.net
AppSearch is the action that performs the registry search that you defined.
You need to add the tag to the and
tags. See the Wix.chm file. Then you should see the
registry search in the log file.
Jim Williams
-Original Message-
From: Colin Fox [mailto:greenene...@gmail.com]
Sent
Do you have Appsearch in the InstallExecute sequence? Also, you could check
the log file and see what is happening.
Jim Williams
-Original Message-
From: Colin Fox [mailto:greenene...@gmail.com]
Sent: Monday, December 22, 2008 9:46 PM
To: wix-users
Subject: [WiX-users] Install location
Sorry for the spam folks, I forgot reply went back to the list.
Jim Williams
425-221-0289 m
-Original Message-
From: Jim Williams [mailto:jimwilliam...@comcast.net]
Sent: Tuesday, December 16, 2008 10:39 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject:
laid off on 12/1 (along with 40 others) and
now and looking for something again... groan.
Thanks,
Jim Williams
425-221-0289 m
--
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of
Yes, as Robert suggested, you could register the COM stuff using the
element.
Jim Williams
-Original Message-
From: Kapoor, Anupama [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 18, 2008 10:38 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] invoking batch file
You might want to try deferred execution instead of immediate. This will run
the custom action after InstallFinalize when the install script is run.
Immediate causes it to be run when it is encountered when creating the
installation script.
Jim Williams
-Original Message-
From
If the old MSI and new MSI file have the same product code then this
makes sense. Trying to install the new MSI is going to find that the
same product already exists so doing a REINSTALL will try to reinstall
the old product. Doing a new install will say it is already installed.
Jim Williams
It looks to me like those properties begin 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
You don't have the property spelled the same in all instances. I see
INSTALLLSFILES (with an L in the middle) and INSTALLPSFILES (with a P in
the middle).
Jim Williams
-Original Message-
From: Sandeep Gautam (HCL Technologies Ltd)
[mailto:[EMAIL PROTECTED]
Sent: Monday, Oc
See http://msdn.microsoft.com/en-us/library/aa372379(VS.85).aspx which
talks about the Upgrade table to get a start on what you need to do.
Then use the WiX equivalent XML tags to define what you need. I'm
hoping you defined an UpgradeCode GUID in your first version though.
Jim Wil
Try: msiexec /a package.msi TARGETDIR=C:\users\volker\test\
Jim
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Volker
Enderlein
Sent: Monday, June 16, 2008 2:59 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] How to forc
Thanks Bob, that did the trick!
Jim
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson
Sent: Monday, June 09, 2008 10:21 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Problem with Light 2.0.5805.0
Jim
turn code '0x1'
Any ideas of what may be causing this? Could this be related to the
mergemod.dll problem that I've seen in some of the posts in the past
week or so? I downloaded the binaries a few weeks ago so it should have
the latest files.
Thanks in advance,
Jim Williams
In
Thanks for making this list subscription-only. My junk mail has gone
from 10 or more a day to zero!
Thanks,
Jim Williams
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008
See http://msdn.microsoft.com/en-us/library/aa368012(VS.85).aspx
Look in the section called "Access Prefixes" for the $ and ! characters
used to reference feature IDs.
Jim
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Hammad
Butt
Sent: Fr
Use .
Jim
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Kunal
Desai
Sent: Monday, May 12, 2008 4:08 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] deleting old files
1) I create an installer based on the files in a particu
It is probably failing because you are trying to invoke an installer
when an installer is already running. You need to install separate
installers sequentially, not from within one another. You would need a
bootstrapper to do that.
Jim
From: [EMAIL PROTECTED]
You might try checking the OriginalDatabase property.
Jim
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bir, Steve
Sent: Friday, May 02, 2008 12:09 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How do you get an msi's filename?
Williams
Sent: Friday, April 25, 2008 10:48 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Localizing properties in WiX 2.0
Wouldn't you need to change your code to:
$(loc. PREVENT_DOWNGRADE)
Jim Williams
-Original Message-
From: [EMAIL PROTECTED]
[m
Wouldn't you need to change your code to:
$(loc. PREVENT_DOWNGRADE)
Jim Williams
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Alex G
Sent: Friday, April 25, 2008 9:42 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Local
My best guess here would be, after installation, to check the registry
using regedit to see that the value of the property INSTALLLOCATION had
the proper value for the path to the DLL substituted. Or you could try
replacing the file:///[INSTALLLOCATION]TAScriptAPI.dll entries with a
reference to t
The dollar sign ($) on the front of the component name MyVbsCa means to
use the value of action state of the component, that is, what is going
to be done to the component. ">.2" means to check if the action state
is greater than 2, where 2 means "not present or installed" or being
uninstalled. Th
Maybe I am misunderstanding your question, but wouldn't you just leave
off the square brackets and just use ENABLED in the condition? You
don't need square brackets in condition syntax as Windows Installer
treats names as properties.
Jim
From: [EMAIL PROTECTED]
Dumb question, but aren't you missing a double-quote after
DATABASELOGINS and before Value=?
Jim
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Robert
O'Brien
Sent: Friday, April 11, 2008 2:54 PM
To: 'wix-users@lists.sourceforge.net'
Subject:
It looks like it is failing because it is trying to query from two
tables, _AppMappings and Error, that don't exist in your MSI file. The
2205 error means the table does not exist, as does 2228 when querying
it. You may have to define these tables to get it to work properly.
Jim Wil
s WiX source. However, according to the WiX
documentation, this should be used in vary rare circumstances.
Jim Williams
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Andres
Aguiar
Sent: Friday, April 04, 2008 3:29 PM
To: wix-
I think you need to code it as:
Jim
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of James
Burgess
Sent: Monday, February 04, 2008 12:16 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Substituting values with Candle
Hi,
I'd like to use
I don't believe you need to have more than one cab file per media
element. Each media element can point to the same physical disk (that
is, using the same disk label and disk prompt). In one of my setups I
have 10 cab files (they came from separate merge modules) and they are
all on one disk.
Ji
I believe the Environment WiX element maps to a row in the Environment
table. The Name column only allows for a text string (which is not
further evaluated) and not a formatted string (which allows property
replacement), so I think you are hosed but I could be wrong.
Jim
-Original Message
her custom attributes in the future.
Jim Williams
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of SaiTeja
Sent: Thursday, November 22, 2007 10:14 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Custom Action type 1042 and 18
Hi Jim
Now I ne
It looks like they are checking a component's installation action, that
is, what the installer intends to do with the component. In this case,
"$C__installscript" is the component ID (from the component table) and
">2" means check to see if we are trying to install the component or run
it from sou
IL PROTECTED] On Behalf Of SaiTeja
Sent: Friday, November 16, 2007 12:47 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Custom Action type 1042 and 18
Hello Jim,
I replaced Execute with "deferred"
now is showing when i open orca type 11346.
But I want type should be 1
I think you want Execute="deferred".
Jim
>below is my custom action.
>
>Impersonate="no" TerminalServerAware="no"
ExeCommand="DisableBrowseInPlace"
>Execute="immediate" Return="check" />
>
>When I open msi with orca, it is showing type as 2066. But I want type
>should be 1042
>
>Could you tell m
Another hackneyed solution would be to edit the images and color the
background the same as the background color of the installer dialog. I
did this for one of our bitmaps and it gives the affect you want without
needing transparency support.
Jim
-Original Message-
From: [EMAIL PROTECTED
"Richard" <[EMAIL PROTECTED]> writes:
> For testing a product during development, I recommend that people have
> a way to reset their test environment and always install the product
> fresh. They can test upgrading and patching after a release has been
> made. By resetting their environment to a
ct: Re: [WiX-users] Doing QFEs With WiX
In article
<[EMAIL PROTECTED]>,
"Jim Williams" <[EMAIL PROTECTED]> writes:
> Is there some way to define a QFE-like mechanism by using WiX?
Windows Installer addresses updates as patches, minor upgrades, or
major upgrades. I r
TED]
Sent: Monday, October 29, 2007 11:21 AM
To: Jim Williams; WiX-users@lists.sourceforge.net
Subject: RE: Doing QFEs With WiX
In WiX v2, you should be able to create patches using the PatchCreation
element. The process is documented in the chm. It will build you a PCP
file which you then can to pu
I am a little behind on keeping up with the latest updates, but am
currently using WiX 2.0.3719.
Jim
From: Peter Marcu [mailto:[EMAIL PROTECTED]
Sent: Monday, October 29, 2007 11:14 AM
To: Jim Williams; WiX-users@lists.sourceforge.net
Subject: RE: Doing QFEs
easy installation of QFEs?
Thanks,
Jim Williams
Intrinsyc Software International, Inc.
11130 NE 33rd Place, Suite 200
Bellevue, WA 98004
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
425.732.4904
-
This SF.n
49 matches
Mail list logo
