I'm using heat to generate the fragment for my COM object. After installing
the MSI, the CLSID entries are not created in the registry. Should I add
Registry elements to my WXS file manually or am I doing something wrong?
Thanks,
Dariel
-
Please disregard. Apparently when MSIUSEREALADMINDETECTION is set, it changes
the AdminUser meaning as specified in the MSDN documentation:
http://msdn.microsoft.com/en-us/library/aa816403(VS.85).aspx
Dariel
-Original Message-
From: Dariel Marlow [mailto:dmar...@microsoft.com]
Sent
I'm attempting to disallow the installation/uninstallation of the MSI unless it
is executed from the bootstrapper (which has a requireAdministrator manifest)
or from an elevated command prompt.
I'm experiencing some inconsistencies with the properties in the subject line.
I set the MSIUSEREALAD
; number of examples in the WiX custom action code using it.
>
> On Sun, May 2, 2010 at 7:03 PM, Dariel Marlow
> wrote:
>
>> I've followed the example on MSDN (
>> http://msdn.microsoft.com/en-us/library/aa367525(VS.85).aspx) about
>> adding custom actions to the
I've followed the example on MSDN
(http://msdn.microsoft.com/en-us/library/aa367525(VS.85).aspx) about adding
custom actions to the progress bar, however, only the action text updates. The
progress bar does not move. Does anyone have an example of how to update the
progress bar from within a cu
I've had luck naming the custom action property to the same name as the custom
action which needs the data. For example:
Also, I found that if you have your Value field formatted in such a way
(KEY=VALUE;KEY=VALUE;...), your session's CustomActionData property formats it
properly in the
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
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
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:
Currently, when uninstalling from Programs and Features it uses a /x to remove
the product. This, however, does not show the UI with its options. Is there a
way to change the default behavior of the UninstallString? I've searched online
and found that setting ARPNOREMOVE causes the UninstallStri
Sent: Saturday, April 10, 2010 7:02 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] using value of checkbox in deferred custom action
On 4/9/2010 1:03 AM, Dariel Marlow wrote:
> What's the proper way to set the custom action data to the value of the
> checkbox control for
What's the proper way to set the custom action data to the value of the
checkbox control for a deferred custom action? Currently, it seems the value is
being set after the ExitDialog Action and after the custom action has executed.
1. Does WIX support MSI files larger than 4GB? If so, what's the best
practice on very large MSI files? I'm aware of the CAB file limitations, but
I've also run into WIX complaining about large files even if they aren't being
placed into a CAB file. I read briefly in the DTF chm that there
13 matches
Mail list logo
