The latest version is 2.0.4208.0 –
so your’s is about 9 months old – its very likely the bug was fixed
in that time. Please try the latest release and let us know how it goes.
Derek
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brower, Jason
Sent: Monday, J
Yes, I believe that is already supported
in WiX 3.0 J
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Michael Osmond
Sent: Monday, June 19, 2006 8:13
PM
To: [EMAIL PROTECTED];
wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Another
Sequencing issue
Is it a terminal server session?
From: Don Tasanasanta [mailto:[EMAIL PROTECTED]
Sent: Monday, June 19, 2006 4:54
PM
To: Bob
Arnson
Cc: [EMAIL PROTECTED];
wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] What
makes ClickThrough per-user?
i tried it on win2000 and
The Id used in Merge and MergeRef is completely
arbitrary. It’s used by wix to match up the Merge and MergeRef
elements. It can be whatever you want it to be.
The Id used in the Module element, however, must be a legal
identifier since it’s used to populate the ModuleSignature table.
Derek,
A further question on the sequencing of wix CAs, will 3.0
have someway for us to apply conditions to the CA actions as well without having
to modify the wixlibs? I have occasionally thought it useful to suppress
the IIS or XML actions during a REINSTALL.
Michael
From: [EMAIL PRO
WiX v. 2.0.3309.0
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: Monday, June 19, 2006 1:55
PM
To: Brower, Jason; Vitaly Dolya;
wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Patching
Problem
I also have found a bug for the
PatchCreation.CleanWorkingFolder
Hi,
Has anyone had any
experience with performing a major upgrade where there are multiple instances of
the target application installed. That is you have used a transform to
change the product code and installed with MSINEWINSTANCE. How can
you tell which of the installed instances is
i tried it on win2000 and it worked fine so i went to a
different xp machine and it worked fine.
my test machine is 2003 server.
can someone with user access not install on
2003 server?
__
Don Tasanasanta
VIACK Corporation
425-605-7423
From: Bob Arnson [mailt
It's probably related to this:
http://msdn.microsoft.com/library/en-us/msi/setup/authoring_modulesignature_tables.asp
-Francis
On 6/13/06, Zhong Xinyi <[EMAIL PROTECTED]> wrote:
Hi all,I have a question regarding the way to reference amerge module. Based on a wix tutorial i saw on the
web,
I rather agree with you, considering REINSTALLMODE parameter ("amus" -
Force all files to be reinstalled, regardless of checksum or version.)
it seems logical, that files must be updated. Different behavior, that
depends on WholeFilesOnly parameter looks more confusing to me.
Nevertheless IMO i
I also have found a bug for the
PatchCreation.CleanWorkingFolder attribute. This maps to the DontRemoveTempFolderWhenFinished
value in the Properties table of the pcp file. If I set
CleanWorkingFolder=”yes” then DontRemoveTempFolderWhenFinished
becomes 1 when it should be 0 (values are op
I would agree that this is a problem –
but since the contents are different, the files should be included as part of
the msp. In fact later down in the log it even includes the line: “Including
entire file: 'C:\build\**\latest\.\PFiles\**\bin\**.dll';” Basically, the file is
I need to show some message boxes from DLL during MSI CustomAction.
Is there any way to get HWND of current MSI UI to pass to the MessageBox
as a parent wnd?
--
Best regards,
Peter G. Sakhno
C-MAP RUSSIA Ltd
http://www.c-map.ru/
___
WiX-users mailing
Title: [WiX-users] wix3: history.txt
I'll see what I can
do.
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Frederik Carlier
Sent: Monday, June 19, 2006 1:29
AM
To: Thomas Hecker;
wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] wix3:
history.txt
Title: Msi localization
You need to set Product/@Codepage –
do not set SummaryCodepage at all – its unnecessary since it defaults to
1252.
Derek
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of KERROUMI Rachid
Sent: Monday, June 19, 2006 2:02
AM
To:
wix-users@l
Title: Msi localization
Hi,
I'm using wix and Difxapp to install drivers. Until now i've just generate English packages… and all is ok.
The structure of my xml files is:
A Xml for the driver component => compiled to a msm
A Fragment Xml which describe my GUI with the interface strings
Title: [WiX-users] wix3: history.txt
Yes, I second that request!
Frederik.
De: [EMAIL PROTECTED] en nombre de Thomas HeckerEnviado el: lun 19/06/2006 10:01Para: wix-users@lists.sourceforge.netAsunto: [WiX-users] wix3: history.txt
I read this proposal some time ago here around, but I just wa
I read this proposal some time ago here around, but I just want to refresh it
in your minds :-)
It would be useful to insert some kind of seperator in the history.txt file
so we users can recognize more easily what actually has changed.
(btw: between 1811 and 1814 nothing has changed according to
No problem with this. I would have to install it, but that's all.
--
View this message in context:
http://www.nabble.com/RFC%3A-Moving-Wix-3.0-to-use-the-.NET-Framework-2.0-t1788371.html#a4932005
Sent from the wix-users forum at Nabble.com.
___
WiX-
19 matches
Mail list logo
