I am still getting this problem with v3.0.4707.0, does anyone have any
ideas?
Neil
-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: 05 November 2008 18:18
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] LGHT0001 The operation comple
I have the same problem (among others)
--Curtis
On Fri, 7 Nov 2008 15:08:57 -0800, "Rob Mensching"
<[EMAIL PROTECTED]> said:
> Very strange. Can you try running light from the command-line directly
> and see if the error message comes out? If so, then this would be a bug
> in Votive. There mig
Ah I think that was exactly it, thanks! I had logic that was detecting
newer version but the Upgrade block was still using UpgradeID to set the
flag. I changed it to use CurUpgradeID and I think things are working now.
Thanks!
On Fri, Nov 7, 2008 at 4:44 PM, Ian Elliott (Excell Data Corporation
I am able to change now but does not work as expected.
For e.g in the below code everything works fine in default install location
i.e
c:\program files\mycompany\Merge Product
c:\program files\mycompany\My Product
But if changing the installlocation in the destination dialog even
then the merge
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: Frida
Hey Richard,
This sounds exactly like what I want to do, but I think I'm not quite
understanding things correctly. Here's what I'm trying to do now. I now
have two upgrade IDs, UpgradeID is the original that I've been using and
CurUpgradeID is one I just added. I also reset my InstallVersion to
They are all in "messages.xml" but we haven't done the work to translate them
into the WiX.chm file. Honestly, we try to make the errors self explanatory so
you don't have to go look somewhere else... that's why many error messages are
three lines long.
-Original Message-
From: David
Happily will I junk earlier versions. I'll download 3.0.4707.0
--
John M. Cooper
-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: Friday, November 07, 2008 3:40 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] light.exe : erro
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 PROTECTED]
Sent: Friday, November 07, 2008 15:37
To: General discussion for Windows In
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 In
Thanks for the prompt reply ... I cut-and-paste the CANDLE and LIGHT
command lines reported by VS2005 into a CMD window ... here's the output
from the LIGHT command-line invocation:
---snip---
Microsoft (R) Windows Installer Xml Linker version 3.0.4318.0
Copyright (C) Microsoft Corporation. All
The FRD test run I just finished produced an MSI of 554.4 megs. This is
without the unit tests and the logs.
--
John M. Cooper
-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: Friday, November 07, 2008 3:31 PM
To: General discussion for Windows Installer XML too
How large? Maybe we're hitting the size problem a different way.
What is the latest version of the WiX toolset that you are using?
-Original Message-
From: John Cooper (Volt) [mailto:[EMAIL PROTECTED]
Sent: Friday, November 07, 2008 15:18
To: General discussion for Windows Installer XML
In article <[EMAIL PROTECTED]>,
"Colin Bleckner" <[EMAIL PROTECTED]> writes:
> Which means that what I'm doing isn't a great long term solution. Is there
> another way to guarantee that my product will replace all of my previous
> ones without bumping the max version on every build?
Produc
Just the flat release directory I'm working with right now has 21,297 files.
But the "goal" install optionally includes a good chunk of the source tree to
the tune of slightly over 330,000 files.
--
John M. Cooper
P.S. I don't make the requirements, I just try to implement them. :)
-O
If you use major upgrades only, you can use third field to indicate the new
version.
-Original Message-
From: Colin Bleckner [mailto:[EMAIL PROTECTED]
Sent: Friday, November 07, 2008 2:55 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Better way to
How many 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_F
Look at description for ICE61
(http://msdn.microsoft.com/en-us/library/aa369005(VS.85).aspx). At the very
end there is a Community Content section. Looks like there is a bug in ICE61.
-Original Message-
From: John Cooper (Volt) [mailto:[EMAIL PROTECTED]
Sent: Friday, November 07, 200
I get the same error with the latest beta. I gather I've run out of memory
suds?
--
John M. Cooper
-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: Friday, November 07, 2008 3:07 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users]
Very strange. Can you try running light from the command-line directly and see
if the error message comes out? If so, then this would be a bug in Votive.
There might already be a bug open on VS2005 and this... VS2005 itself
apparently has a couple issues around this sort of thing IIRC.
-
That build is 5 months old. Lots of bugs fixed in that time. However, this
particular issue sounds like BUG:1714496. Note the fix for the bug is to print
out a friendlier error message not to change the underlying Windows Installer
to accept more files.
-Original Message-
From: John
Hrm, looking around a little bit it appears that the major version should
have a max value of 255:
http://msdn.microsoft.com/en-us/library/aa370859(VS.85).aspx
Which means that what I'm doing isn't a great long term solution. Is there
another way to guarantee that my product will replace all of m
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 o
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 over an existing installation, I've
been doing this:
Every time I do a build I bump the InstallVersion "X" up one. It's
obviously a hack, but h
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
I'm just starting to use WiX, and have installed the v3 Beta
(3.0.4318.0, including ProjectAggregator2) and using VS 2005. I am
getting some error messages when building the WiX project like this (yes
all on one line):
C:\IPDS\Dev\DI3_Installer\Product.wxs(37,0)Error LGHT0094:
C:\IPDS\Dev\DI3_Ins
I am trying to build MSI with no cab and all files uncompressed. I have
the following Media element declaration:
Myproject.wxs(1266): error LGHT0135: The file '_SOMEDATAFILE.TXT' should
be compressed but is not part of a compressed media. Files will be
compressed if either the File/@Compre
Answering my own post - the problem was that Product element must have
compressed="no" attribute set when building MSI with no CAB.
I had this attribute set to "yes".
-
This SF.Net email is sponsored by the Moblin Your Move
Hi,
Did it work with Wix?
http://support.microsoft.com/kb/313372:
SYMPTOMS
When you use the MSXML 4.0 Document Object Model (DOM) methods
(selectNodes and selectSingleNode) to run XPath queries against an XML
document that specifies a default namespace declaration, the matching
node or nodes are
Put the Merge element under the Directory you want retargeted to.
-Original Message-
From: vivek.anandan [mailto:[EMAIL PROTECTED]
Sent: Friday, November 07, 2008 11:00
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Changing default install paths in msm
I am using merge modules
Usually, the issue is that there is some configuration you do while deploying
then you need to re-sign the application configuration files. It's a poor
design on ClickOnce's part.
-Original Message-
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Friday, November 07, 2008 10:31
To: Gen
I am using merge modules created using InstallShield in Wix.
Any idea how to change the install path for those merge modules?
They dont pick the install path but use the default path on these merge
modules.
I am able to change the install paths for those merge modules using
Installshield.
thanks,
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
Pierson Lee (PIE) wrote:
> 1. Mage.exe generates Application Manifest
>
> 2. Mage.exe signs Application Manifest
>
Why not create the manifests as part of your build and ship them in the
installer ready to go?
--
sig://boB
http://joyofsetup.com/
---
Peter Vestergaard wrote:
> The custom action is not run twice, because the checkbox dialog is located
> after the progress dialog. Maybe I don't need to list it in the
> InstallExecuteSequence...
>
When you schedule a custom action in InstallExecuteSequence, it runs as
part of the install.
>
Check out the conversations about the difference between XmlFile and XmlConfig.
XmlConfig is powerful enough to handle this scenario. XmlFile isn't.
-Original Message-
From: MadhaviAthota [mailto:[EMAIL PROTECTED]
Sent: Friday, November 07, 2008 03:58
To: wix-users@lists.sourceforge.net
You'll need to go through the MSXML documentation. I've only successfully done
this once myself and it took me a few hours of pouring over the MSXML
documentation to get the magical incantation just right. Unfortunately, I
don't have access to that code anymore and I don't have a few free hour
I don't think that the website harvester has been maintained. The guy that
wrote it (a long time ago) left us (a long time ago).
-Original Message-
From: Joe Osman [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 06, 2008 17:38
To: General discussion for Windows Installer XML toolset
The summary information stream is controlled by the "Package" element. What do
you have as the Package/@Language attribute? If it is absent, I expected it to
default to whatever you specified in the Product/@Language (to avoid this
problem ).
-Original Message-
From: Dave Horne [mailt
Hello Everyone,
Please let me know how we can remove a user during uninstallation with a
known username.
Thanks and Regards,
Surekha Vuchuru
-Original Message-
From: Richard [mailto:[EMAIL PROTECTED]
Sent: Friday, November 07, 2008 9:52 AM
To: General discussion for Windows Installer X
Hi All,
I am working on Wix DTF. Generated a C# dll that gets the name of all
the folders available in a parent folder and sends the result to a Wix
CA Property.
I am getting the following error
I am getting this error during installation.
Error 1723. There is a problem with this Windows Instal
Stupid newbie here.
I'm following examples with the Language attribute of the Product element
set to 1033 and yet I get the error below?? Is this a wix config issue?
Also it is strange that the help file doesn't list "Language" as an
attribute for the "Product" element, but it is required sinc
Hi,
Does anyone has any example of XPath expression that added new node
to Xml with schema?
I tried all the variants, but it was not working.
Also I tried to execute expression with "XSLPattern"
(/SolutionProfile//[EMAIL PROTECTED]'Apps']//Modules) instead of "XPath".
But it adds new node wich con
Thank you Richard.
Regards,
Surekha
-Original Message-
From: Richard [mailto:[EMAIL PROTECTED]
Sent: Friday, November 07, 2008 9:52 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Modifying a property value during installation
doesnot persist until
Yes, this is by design. Windows Installer doesn't persist properties for
you. If you want to persist a property from install time to have the
same value at uninstall time, then use the Registry table to write the
property value into the registry and use AppSearch to read it out of the
registry.
In article <[EMAIL PROTECTED]>,
Ravi Patt <[EMAIL PROTECTED]> writes:
> 1) How do I change the installshield projects (*.ism) to wix xml document.
The .ism file is just an MSI database. You can extract WiX xml from that
directly, or you can use your built MSI.
> 2) How do I convert the in
Hello All,
I am creating a user element that has [UserName] property set to
"DefaultUser" as its value. We give the option of changing [UserName]
during installation. So, the installer creates a user using the modified
username say "Test123". [UserName] property is modified to "Test123$"
and user
Ah... Yep, if it's a deferred execution CA then you'll need to use the
CustomActionData property to pass data to it. SecureCustomProperties is
for passing data from the UI to the MSI server side. In this case you
might even need both.
Have a look at Obtaining Context Information for Deferred Execu
It could also be that you're setting the property to the string "1" and
testing for the numeric value 1. Try testing for "1" in your condition
instead.
Cheers,
James
-Original Message-
From: Richard [mailto:[EMAIL PROTECTED]
Sent: 06 November 2008 18:22
To: General discussion for Windows
Hi All,
I have a web.config file which needs to updated on MSI installation. I have
done this with xmlFile element.
When I do an in-place upgrade on the MSI which is a minor upgrade, I need to
update a new string in Web.config, which is not working, when I try to
update, and erroring out if som
Thanks for your information.
Thanks,
Changfeng
-Original Message-
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Friday, November 07, 2008 2:42 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Why does cancel dialog locate top of main installation
d
And in this, you guys have already helped me a lot, giving me enough food for
thinking and trying :}
Rob Mensching-2 wrote:
>
> It all depends on how you want to organize your non versioned flies. I
> still do not pretend to understand all the intricacies of your scenario so
> we're just tryin
It all depends on how you want to organize your non versioned flies. I still
do not pretend to understand all the intricacies of your scenario so we're just
trying to give you options to consider.
-Original Message-
From: zett42 [mailto:[EMAIL PROTECTED]
Sent: Friday, November 07, 2008
Wouldn't Windows Installer then want to update ALL non-versioned files
instead of only the components which actually have changes in them?
I would rather use one dummy versioned file per directory to avoid this. But
then there would be no use for a companion file since the versioned file can
act a
If you have a dummy file that has a version resource in it, you can companion
all of the non-versioned files to the dummy file and implicitly provide them a
version. It may work out well.
-Original Message-
From: zett42 [mailto:[EMAIL PROTECTED]
Sent: Friday, November 07, 2008 00:57
To:
I don't really see how companion files would help in this situation.
Alexander Shevchuk wrote:
>
> You may want to use Companion files
> (http://msdn.microsoft.com/en-us/library/aa367997(VS.85).aspx) in this
> situation.
>
>
>
> -Original Message-
> From: zett42 [mailto:[EMAIL PROTEC
56 matches
Mail list logo
