For DLL (and EXE) custom actions, the bitness is determined by the action's
binary itself, not any marking in the MSI. In the case of DTF, the initial
bitness employed will be the bitness of the sfxca.dll packaged by the
wrapping action of the DTF build process. I haven't looked at the source
code
If you mark your custom action as a 64-bit action it should run in a 64-bit
process. I haven't tried it with DTF since I write all my custom actions in
C/C++.
On Sat, Oct 24, 2009 at 7:37 PM, Dave Kolb d...@dotnetcodeslingers.comwrote:
Good information Blair and thanks. I did not know about the
Good to know for future reference as I have take Blair's good advice and no
longer fool with CA's to touch the registry or the event source and do those
with wix elements. My only custom action left decodes a des256 string to get
credentials for when I create the service and that works well.
Candle doesn't like Keypath on that element: error CNDL0004: The RegistryKey
element contains an unexpected attribute 'KeyPath'.
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Saturday, October 24, 2009 1:22 AM
To: 'General discussion for Windows Installer XML toolset.'
Hi Blair, you probably meant adding KeyPath to a RegistryValue element.
After I did that, I got this to somewhat work but only the HKCU key gets
created and not the HKLM key. No complaints during install in the log file.
I am doing a perMachine install and it seems if anything it should do the
Well I flipped the order of the components in the directory node and the
feature node and still only the HKCU key got installed.
I think I will just have a custom action update/delete the registry for me
since I have to do that with event logs anyway.
- Dave
-Original Message-
From:
Why do you need a custom action for event logs?
Also, writing/deleting per-user content via installation packages rarely
works out as well as people hope because you can't modify all the user
profiles. Only the current user. In general, HKCU stuff should be managed by
the application.
Finally, a
I need a custom action to create the event source as otherwise when my 2
services and app try to write to the event log they fail. If the
services/app tries to create the event source, if it does not exist, there
is a supposed delay and the event log cannot be written to and this indeed
seems to
Back in the good-old-days we simply wrote in the registry until it looked
like what this page describes:
http://msdn.microsoft.com/en-us/library/aa363661(VS.85).aspx
However, the Wix Util Extension does have an EventSource element that seems
to fit the billing. Does it not work for you?
If you
Good information Blair and thanks. I did not know about the EventSource
element but should have guesses there likely was one.
I will rethink what I am doing with the registry given your guidelines.
Especially since I just realized that my custom action, built for Any CPU,
is running against the
Thanks John!
-Original Message-
From: John H. Bergman (XPedient Technologies)
[mailto:john.berg...@xpedienttechnologies.com]
Sent: Saturday, October 24, 2009 11:39 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How do I add both a HKLM and a HKCU
During install, I am trying to add both an HKLM key and an HKCU key for my
product. My wxs looks like the below. When this compiles I get the error
ICE57: Component 'C_HKCU_RegistryEntries' has both per-user
and per-machine data with a per-machine KeyPath .
I have both
Try adding KeyPath=yes to each of your two RegistryKey elements.
-Original Message-
From: Dave Kolb [mailto:d...@dotnetcodeslingers.com]
Sent: Friday, October 23, 2009 6:34 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: [WiX-users] How do I add both a HKLM and a
13 matches
Mail list logo
