My team wants the capability to install multiple copies of an MSI on a given
host with different tags appended to the ProductName (so the configuration
specialist can identify different instances in the Control Panel.
Obviously, I'd have to turn off detection of older or newer MSI's.
How best
,
if you dont mind installing your tool.
-Original Message-
From: John Cooper (Volt) [mailto:a-jc...@microsoft.com]
Sent: 19 July 2010 18:56
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] {INSTALLLOCATION] Not Expanding to It's Value in a Type 2
Custom Action
I have a Type 2 Custom Action that isn't working right. LG_IIS7Installer.exe
is running, but INSTALLLOCATION is not expanding. INSTALLLOCATION is set as a
property= on the msiexec command line, and the files get installed into the
right places. But instead of he path expected,
Did you include a reference to the IIS Extension lib? You may also need to use
a PropertyRef before you can use these properties.
--
John M. Cooper
-Original Message-
From: Andres Juarez [mailto:andresj_...@hotmail.com]
Sent: Tuesday, June 08, 2010 11:30 AM
To:
What is the size and nature of the project? Currently, I'm employed as a
contractor (where one of my jobs is writing Wix Installers to deploy their
products) at Microsoft. If the project were on the small or simple side, I
could probably do it on the side.
--
John M. Cooper
-Original
Well, it's certainly not a Wix issue, but environment with batch files can be
affected. Check out SETLOCAL ENABLEDELAYEDEXPANSION (setlocal /?). Especially
if the environment variables are used in loops, the standard dereferencing
(%some_variable%) will not work properly. Enabling the above
Here's the portion of the WiX:
Component Id=CDEFAULTASPX
Guid=579C6861-0A71-4018-9307-DFECEA33C362
File Id=FDEFAULTASPX
Name=Default.aspx
DiskId=1
Source=$(var.WebPath)\Default.aspx /
util:XmlFile
restrictive?
Thanks,
Mike Carlson
-Original Message-
From: John Cooper (Volt) [mailto:a-jc...@microsoft.com]
Sent: Thursday, May 06, 2010 12:02 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] XMLFile not Finding file to Edit Even Though File is
Verified
The Default.aspx lacked an ?xml version=1.0 encoding=utf-8? line, but
both Web.config files have it and are treated in exactly the same way as the
original Default.aspx.
--
John M. Cooper
Volt at Microsoft
-Original Message-
From: John Cooper (Volt) [mailto:a-jc...@microsoft.com]
Sent
Message-
From: John Cooper (Volt) [mailto:a-jc...@microsoft.com]
Sent: Thursday, May 06, 2010 2:32 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] XMLFile not Finding file to Edit Even Though File is
Verified There
Yes, it is definitely possible
, uninstall, and/or
various patch scenarios.
-Original Message-
From: John Cooper (Volt) [mailto:a-jc...@microsoft.com]
Sent: Thursday, May 06, 2010 3:32 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] XMLFile not Finding file to Edit Even Though File
I think what you want to do could be done with a:
1) Launch condition dependent on a property;
2) The property is set based on a Registry Search, File Search, or Component
Search.
--
John M. Cooper
-Original Message-
From: Volnei dos Santos [mailto:vol...@gmail.com]
Sent: Thursday,
Back building my monster installer. I have a troublesome spot.
During the linking of the final MSI, light.exe attempts to CAB about 0.5 G of
msm. At this juncture, 3.0.4923.0 gives me a LGHT0001 : Unable to find an
entry point named 'CreateCabCancel' in DLL 'winterop.dll'.
So, is it
As an addendum, this LGHT0001 error did NOT bring light.exe to a screeching
halt. It continues to grind away at the remaining cabs.
--
John M. Cooper
-Original Message-
From: John Cooper (Volt) [mailto:a-jc...@microsoft.com]
Sent: Tuesday, February 10, 2009 1:52 PM
To: wix-users
I had to send to original message twice to get through security filter--looks
like the subject line took a hit.
--
John M. Cooper
-Original Message-
From: John Cooper (Volt) [mailto:a-jc...@microsoft.com]
Sent: Tuesday, February 10, 2009 1:52 PM
To: wix-users@lists.sourceforge.net
] (no subject)
1. The Merge Module spec says there is always a cabinet file.
2. The LGHT001 error was fixed in a later build.
-Original Message-
From: John Cooper (Volt) [mailto:a-jc...@microsoft.com]
Sent: Tuesday, February 10, 2009 14:57
To: General discussion for Windows Installer XML
The fourth place (the revision) is generally ignored by MSI.
--
John M. Cooper
-Original Message-
From: Sandeep Prakash [mailto:sandeep.prak...@microsoft.com]
Sent: Thursday, January 29, 2009 2:49 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users]
to get rid of
Ug, bug. Can you file this on SourceForge? Should be able to get a fix next
week. Be sure to put it under the v3.0 Group and light Category.
-Original Message-
From: John Cooper (Volt) [mailto:a-jc...@microsoft.com]
Sent: Monday, January 26, 2009 09:20
To: General
I can't seem to get rid of this error on my server builds:
1/23/2009 2:57:48 PMCMD:
E:\bt\512100\build\setup\tools\wix\3.0.4707.0\binaries\light.exe -ct 16 -v
-pedantic -ext WixUIExtension -ext WixNetFxExtension -cultures:en-us -loc
Well, taken from the Info Zip website at
http://www.info-zip.org/FAQ.html#limits :
Number of files: 65,546
Uncompressed Size of a single file: 4GB
Compressed Size of a single file:4GB
Total Size of Archive: 256TB
Maximum Path/Filename Length:64KB
for Windows Installer XML toolset.
Subject: Re: [WiX-users] Skipping License Page and Zipping a Folder
I don't understand what this is intended to demonstrate.
-Original Message-
From: John Cooper (Volt) [mailto:a-jc...@microsoft.com]
Sent: Wednesday, January 07, 2009 13:27
To: General discussion
PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Skipping License Page and Zipping a Folder
But the Windows Installer only supports CAB files.
-Original Message-
From: John Cooper (Volt) [mailto:a-jc...@microsoft.com]
Sent: Wednesday, January 07, 2009 14
I'm getting a 2707 error I'm having trouble deciphering. Here's an extract
from the verbose log:
Action 17:13:29: SET_TARGETDIR.
Action start 17:13:29: SET_TARGETDIR.
Action ended 17:13:29: SET_TARGETDIR. Return value 1.
Action 17:13:29: FindRelatedProducts. Searching for related applications
-
From: John Cooper (Volt) [mailto:a-jc...@microsoft.com]
Sent: Tuesday, January 06, 2009 08:45
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Decipher Error 2707
I'm getting a 2707 error I'm having trouble deciphering. Here's an extract
from the verbose log
Although it lacks a sexy UI, the FreeBSD system for packaging up binary builds
has the advantage that it's tarballs can run pre- and/or post-
install/uninstall scripts to either prepare for the install or return the
system back to the state it had before the install.
--
John M. Cooper
whatever is necessary. IMHO, that leads everyone (developers and
users) down the path to unmanageable systems.
-Original Message-
From: John Cooper (Volt) [mailto:a-jc...@microsoft.com]
Sent: Wednesday, December 17, 2008 12:57
To: General discussion for Windows Installer XML toolset
You can use perl with a module like XML::Simple to read in Web.Config. In the
case of XML::Simple, you'd then test for a tree node
$parent-{'ConnectStrings'}. If it doesn't exist, then you'd just add the node
to the tree and flush the tree to Web.Config. Other perl modules can do this
job
When running light.exe in an automated job to build an MSI, I get the following
error message:
Microsoft (R) Windows Installer Xml Linker version 3.0.4207.0
Copyright (C) Microsoft Corporation. All rights reserved.
light.exe : error LGHT0001 : Error HRESULT E_FAIL has been returned from a call
From: Colin Bleckner [mailto:[EMAIL PROTECTED]
Sent: Friday, November 07, 2008 2:40 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Better way to handle upgrades?
Hey all,
I build a lot of installers for my project. In an attempt to make it easy
for users to install a newer version
not to change the underlying Windows Installer
to accept more files.
-Original Message-
From: John Cooper (Volt) [mailto:[EMAIL PROTECTED]
Sent: Friday, November 07, 2008 14:32
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] light.exe : error LGHT0001 : Error HRESULT E_FAIL has been
files? Take a look at the bug I mentioned.
-Original Message-
From: John Cooper (Volt) [mailto:[EMAIL PROTECTED]
Sent: Friday, November 07, 2008 15:10
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] light.exe : error LGHT0001 : Error HRESULT E_FAIL has
: John Cooper (Volt) [mailto:[EMAIL PROTECTED]
Sent: Friday, November 07, 2008 15:18
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] light.exe : error LGHT0001 : Error HRESULT E_FAIL has
been returned from a call to a COM component.
Just the flat release directory
I'm currently using 3.0.4207.0 (it's the latest one in the tree), but I've also
tried 3.0.4318.0 with the same results.
--
John M. Cooper
-Original Message-
From: John Cooper (Volt) [mailto:[EMAIL PROTECTED]
Sent: Friday, November 07, 2008 3:34 PM
To: General discussion for Windows
: error LGHT0001 : Error HRESULT E_FAIL has
been returned from a call to a COM component.
The latest build id 3.0.4707.0. If you're going to use the WiX v3 toolset, you
need to stay more current. We are fixing bugs all of the time.
-Original Message-
From: John Cooper (Volt) [mailto:[EMAIL
34 matches
Mail list logo
