Mike Dimmick wrote:
> KEY_WOW64_64KEY flag to the samDesired parameter of RegCreateKeyEx or
> RegOpenKeyEx. If required, you can delete a 64-bit key from 32-bit code by
> calling RegDeleteKeyEx.
>
The issue isn't Reg*Ex, it's GetNamedSecurityInfo in the SecureObject
CA. SE_REGISTRY_WOW64_32KEY
>>> Comments inline.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson
Sent: 25 March 2008 15:21
To: Sanin
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Re compiling WiX C++ libs for 64-bit
> 2. If so, here is
urce of the registry information.
--
Mike Dimmick
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Sanin
Sent: 30 March 2008 00:12
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Re compiling WiX C++ libs for 64-bit
LOL Just writing registry keys, o
LOL Just writing registry keys, of course, is not the only thing that happens
inside .NET custom actions. Sometimes we have to read a registry key already
written and perform a certain action, or write a new key whose value is not
that easily derived to be handled by the Registry table.
Bob Arns
Sanin wrote:
> 2. Explicitly pass appropriate flag when using registry classes from .NET so
> that automatic redirection does not happen.
>
Why would you go through the hassle of writing a C++ custom action that
loads a .NET assembly to write to the registry when MSI already supports
64-bit r
For the risk of beating a dead horse let me try to explain:
Fundamentally, I want to be able to write custom actions for WiX in .NET. As
we all know WiX at present time cannot call into .NET assemblies.
So we set out to create a simple shim in C++ which has the job of loading a
.NET CLR and invo
To answer my own question:
NO -- the CLR loaded will be 32-bit and all "downstream" calls into .NET
custom actions will run as 32-bit and be victims of registry redirection.
Sanin wrote:
>
> Bob, thanks for your reply.
>
> To make sure let me summarize:
>
> Although my CLR loader, which is a
Sanin wrote:
> Although my CLR loader, which is actually a C++ custom action for WiX, is
> 32-bit IT WILL be able to load the 64-bit CLR into the installer process and
> kick off .NET custom actions, which in turn may write files and registry
> keys without redirection, right?
>
Sorry, I don't
Bob, thanks for your reply.
To make sure let me summarize:
Although my CLR loader, which is actually a C++ custom action for WiX, is
32-bit IT WILL be able to load the 64-bit CLR into the installer process and
kick off .NET custom actions, which in turn may write files and registry
keys without
Sanin wrote:
> 1. Do I have to recompile my shim (i.e. C++ custom action) to 64-bit?
>
Probably not. The WiX custom actions are currently 32-bit because we
were able to work on 64-bit portions of the file system by disabling
file-system redirection when necessary. It's available in wcautil.li
I have a C++ WiX custom action which happens to be a shim to a .NET assembly.
I am now trying to produce a 64-bit version of the installation kit.
Questions:
1. Do I have to recompile my shim (i.e. C++ custom action) to 64-bit?
2. If so, here is the problem:
- existing WiX C++ libraries (wcaut
11 matches
Mail list logo
