That still sounds as if you're adding and removing components from features.
You'll need to do a major upgrade for that.
If you really want to add e.msm's contents in a minor upgrade (which I
wouldn't really recommend) you need to add a new child feature of an
existing feature and attach the me
Error 123 (listed in the first error message) is ERROR_INVALID_NAME:
"The filename, directory name, or volume label syntax is incorrect."
It doesn't like something about the folder name. I'm not sure if the
directory you're trying to share has to already exist at the point that you
create the sha
Hi Venkatesh,
The use of Condition element is different.
You can use it in:
a) inside Component element (that is probably what you want)
...
the component will be installed if the condition is evaluated to true
b) inside the Feature element:
the Feature Level will
Mike,
I have already placed Win64='yes' in the component tag.
FileType
But, it is not working. Any other alternative way???
-Jagath Pabolu
Mike Dimmick <[EMAIL PROTECTED]> wrote:
v\:* {behavior:url(#default#VML);} o\:* {behavior:url(#default#VML);}
w\:* {be
I ahve a radio button where user selects a version of productUnicode Or ASCI)
depending upon I need to install a different binary. I am using condition
statement under feature. Looks like it is not working for me. I donot know what
I am doing wrong here. Please help me.
Code as follows:
FYI, I was able to figure out how to use CAQuietExec by searching through the
mailing list archive.
Thanks,
Kevin
From: [EMAIL PROTECTED]: [EMAIL PROTECTED]: [EMAIL PROTECTED]: RE: [WiX-users]
Problem using Action attribute on Custom elementDate: Wed, 16 May 2007 14:17:37
-0600
Actually th
Thanks for the reply, though I suppose I should've been a been clearer.
Each merge module contains files and is its own component, like this:
* a.msm
directory 1
file-a1.txt
file-a2.txt
* b.msm
Hi Rob,
Copying and pasting from an e-mail from Carolyn Napier who had a look at our
logs relating to this issue:
8<
Error 1316. A network error occurred while attempting to read from the file:
C:\EHS\alec\dev\CTEB.tmp
MSI (s) (F0:14) [14:19:26:471]: Note: 1: 2205 2: 3: Error
MSI (s)
I have a need to have different default install paths based on a
variable that's set by the user choosing a radio button in a previous
dialog. Has anyone tried something like this? I can't seem to figure it
out.
It seems that INSTALLDIR always defaults to whatever I have it set to in
my struct
Mike Dimmick-2 wrote:
>
> 'Everyone' is not a member of the domain but is a Windows well-known SID.
> The CA code in WiX 3.0.2813.0 handles "Everyone" directly. I think, based
> on
> my reading of the code, that you should omit the User/@Domain parameter.
>
> --
> Mike Dimmick
>
Mike: Th
Mike Dimmick-2 wrote:
>
> 'Everyone' is not a member of the domain but is a Windows well-known SID.
> The CA code in WiX 3.0.2813.0 handles "Everyone" directly. I think, based
> on
> my reading of the code, that you should omit the User/@Domain parameter.
>
> --
> Mike Dimmick
>
Mike: Th
Note that for actions, in the UI and execute sequences, the conditions are
simply the inner text of the action's element. For example, see .
Conditions are commonly contained within a block. This is
simply because the greater-than and less-than operators have a different
meaning to XML. The .
Thank for your help.
I know you are just trying to be consistent but when setting the property
(Build in this case). Do you have to escape it with CDATA? If the value you
are setting the property to is 0?
What if I want to conditionally set a property? If the value is empty or
null then I w
You want the Condition element
Which can also check a property such as my Build property
This is how I declare the property that is checked in the condition.
Check the docs to see what elements can have conditions:
http://wix.sourceforge.net/manual-wix2/wix_x
I'm assuming that you're installing the MSMs as files i.e. they're for your
end-users to use to build their own installers, therefore the fact that they
are MSMs is not relevant.
The component rules say you're not allowed to change the makeup of a
component. If all these MSMs are in one compone
I have only found which is a preprocessor instruction. Is there an
equivalent runtime conditional statement? If the installer clicks on a
button I record the fact by setting a property. I want to be able to test
for the values of this property and a conditional like statement
seemed to be what I
I need to create a "ProductName" folder in the
c:\ProgramData\CompanyName\ProductName path under Vista and make its
readable and writeable by all users (by default Windows Vista allows only
the user who created the file to edit the file). In my case, the
product.ini file that will be placed in thi
We've hit an interesting scenario in our work where we're not seeing one
of the MSM's getting applied in a re-install scenario.
We start off with some.msi that contains the following merge modules:
* a.msm
* b.msm
* c.msm
* d.msm
Some.msi now lays down all of the merge m
Actually that was the complete error message:
candle.exe(0,0): Error CNDL0001: Cannot set column 'Action' with a null value
because this is a required field.
Julie hit upon the solution in another reply. I needed to add an "Id"
attribute to the CustomAction Property="QtExecDeferred" listed below
'Everyone' is not a member of the domain but is a Windows well-known SID.
The CA code in WiX 3.0.2813.0 handles "Everyone" directly. I think, based on
my reading of the code, that you should omit the User/@Domain parameter.
--
Mike Dimmick
-Original Message-
From: [EMAIL PROTECTED]
[mail
There's a completely different method in WiX 3.0. 3.0 permits substitution
of data in the compiled .wixobj/.wixlib files at link (light) time. Specify
-dWixUILicenseRtf=path-to-license-file on the light command line.
This is definitely a FAQ.
--
Mike Dimmick
_
Although I'm not havi
I'm trying to create a repository where everyone in the domain have full
control. Here's the code I've tried:
That's the first time I do something similar to that, I used wix
documentation to do some "assessed guessing"... then I got these er
Set Component/@Win64='yes'.
--
Mike Dimmick
_
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of jagath pabolu
Sent: 16 May 2007 13:42
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Registry key creation in 64bit machine.
Hi,
We are trying to create
>From which I deduce that you're writing a 32-bit installer and installing on
a 64-bit machine. A 32-bit application will see the keys as you have written
them.
--
Mike Dimmick
_
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Kevin Burton
Sent: 16 May 2007 13:57
T
There's a completely different method in WiX 3.0. 3.0 permits substitution
of data in the compiled .wixobj/.wixlib files at link (light) time. Specify
-dWixUILicenseRtf=path-to-license-file on the light command line.
This is definitely a FAQ.
--
Mike Dimmick
_
From: [EMAIL PR
I know nothing about WiX 3, but here's how I do it with WiX 2, which may
help: http://www.merlinia.com/mdt/WiXTutorial3.msl
If the Common Public License text is being shown it sounds like you have
not actually replaced the file in the input to the WiX project...
Rennie
_
Here is the scenario. We do the initial installation. Then little if any of
the "properties" (there are about 10 that basically define the app, server
name(s), user name, SMTP server, etc.) change. But the code changes so we
"release" with new features and bug fixes fairly regularly. I want to bui
Using 3.0.2420, no matter what I do, the license.rtf file is ignored and
the Common Public License text is used. I've removed the License Dialog
from the UI completely for the time being, but is this a known issue or
am I missing something or what?
Cheers,
Mark
Computer Software Group Plc |
I edited the original e-mail to put the elements on different lines only.
Try adding an Id attribute to the CustomAction element that sets the
property, i.e., Id='SetProp_QtExecDeferred'. Also, set execution of this to
'immediate'. You also need to call this custom action within the
InstallExecu
Sorry, I think I answered my own question. There is a node called
Wow6432Node that seems to be automatically inserted in the path. My registry
entries were under there.
Thanks again.
Kevin
-
This SF.net email is spo
The actual code looks like:
. . .
Do you think I have a syntax problem? Like I said, I look in the log file
and it appears to be writing values to the registry but using regedit I
don't see any entries.
Kevin
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of R
Hi,
We are trying to create a registry key using Wix for 64 bit targeted
installation as below
FileType
.
FileType.xyz.1
..
But, registry key is getting created under
"HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\" instead of native 64bit hive.
Is the
Running depends on a problem machine is just showing me issues with
MSJAVA.DLL and MPR.DLL. The depends FAQ makes me think they aren't
really issues to be concerned with.
Also, building statically, I don't know of a machine that it does work
on. I have only been testing on my development XP m
I've written a bit about using the element here:
http://www.merlinia.com/mdt/WiXTutorial1.msl (near bottom of page).
Are you looking in the right place? (HKLM vs. HKCU?)
The element has to be inside a element. The
registry entry should automatically be removed when the Component is
uninstal
Brand new just finished extracting last night
ALTERNATIVE MEDICINE DATABASE
Over 1 million records and 72,000 emails in the following categories:
* Nutritionists
* Naturopathy
* Naturopathic Schools
* Naturopathic Remedies
* Naturopathic Physicians
* Naturopathic Medicine
* Naturopath Diet
*
I am trying to use the task and I look in the log file during
installation and it seems to be executing but when I look at the actual
registry the keys and values are missing. Is the full key path automatically
created or should I initially create the registry path? Related to this, how
do I speci
Thanks guys, I'll have a play around with your suggestions and post
back. I did add the Execute="deferred" and Impersonate="no" but this
didn't work on first attempt. Setting @Execute="commit" caused it to
call but the action but it still failed. I'll get back with my results.
Regards, Nigel
Jason Smart wrote:
> If the only differences between two files is that fact that they've been
> recompiled, surely the delta patch would create a smaller .msp file?
Generally true. There's some overhead in the delta patch itself, of
course, and binaries other than executables might not "delta-
38 matches
Mail list logo
