On 4/14/2010 11:07 AM, Dariel Marlow wrote:
> That's exactly why it is of concern; it doesn't remove the temp directory
> after running. The other is not a native-code custom action, both are managed.
>
Probably one is run from an installed assembly and the other is in the
Binary table? Pleas
rom: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Wednesday, April 14, 2010 7:56 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Deferred custom action creates directories in the
installation directory
On 4/13/2010 9:52 PM, Dariel Marlow wrote:
> I have another installer that is run
On 4/13/2010 9:52 PM, Dariel Marlow wrote:
> I have another installer that is running with elevated privileges and its
> deferred custom actions are executing from the windows\installer directory. I
> can't find why one runs from the program files directory while the other runs
> from windows in
ay to specify?
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Tuesday, April 13, 2010 7:15 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Deferred custom action creates directories in the
installation directory
On 4/13/2010 6:11 PM, Dariel Marlow
On 4/13/2010 6:11 PM, Dariel Marlow wrote:
> When running the deferred custom action, a directory is created in the
> installation directory. The log files says that the custom action is being
> extracted to a temporary folder. Why is it not doing this in the typical temp
> directory?
>
Sec
When running the deferred custom action, a directory is created in the
installation directory. The log files says that the custom action is being
extracted to a temporary folder. Why is it not doing this in the typical temp
directory?
Here's the pertinent part of the log file:
...
MSI (s) (0C:
6 matches
Mail list logo
