Arnson-6 wrote:
>
> 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
does not happen.
Hope this makes it clearer.
Bob Arnson-6 wrote:
>
> 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 cust
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:
>
> Alth
redirection, right?
Bob Arnson-6 wrote:
>
> 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
his
target. Where is this coming from?
And more importantly how do I pass ClTask.options values through it?
Obviously a bunch of "standard" defines are already present (see the log)
but i am not sure how i can add my defines to it...
Hope this makes sense.
Thanks.
Sanin
Here is the log
5 matches
Mail list logo
