John Lalande wrote:
> I have reached a solution that makes everyone here happy. It
> incorporates what you suggest but adds a small detail. I cannot
> display a dialog from the ARP uninstall, but I can display a dialog
> from my custom action that informs the user of what is happening. It
>
I have reached a solution that makes everyone here happy. It incorporates
what you suggest but adds a small detail. I cannot display a dialog from
the ARP uninstall, but I can display a dialog from my custom action that
informs the user of what is happening. It offers two buttons: Retry and
Exi
: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] uninstall LaunchCondition
>You didn't answer my question -- you want the uninstall to be canceled;
>you just don't like the "fatal error" message, right?
That's correct, I don't like the "f
You didn't answer my question -- you want the uninstall to be canceled;
you just don't like the "fatal error" message, right?
That's correct, I don't like the "fatal error" message. And neither does my
supervisor.
I understand the solution you are proposing but that user experience is
actually
The CA does not failit merely sets a property.
If I make this change, the uninstall will abort before I get to the launch
condition without a meaningful message to the user.
But the CA has nothing to do with the issue. This issue exists using the
tutorial SampleFirst package where there is
John Lalande wrote:
> I understand where they might be useful; that is why I am using one.
> But my experiments show that a failing launch condition during
> uninstall from ARP always shows the fatal error message after
> displaying the launch condition message.
Correct, that's how ARP works.
Did you set you try telling it NOT to ignore the return value since you want
it to fail if the condition fails, and returning the value
ERROR_INSTALL_USEREXIT from the CA when it fails?
On 1/26/07, John Lalande <[EMAIL PROTECTED]> wrote:
I understand where they might be useful; that is why I am
I understand where they might be useful; that is why I am using one. But my
experiments show that a failing launch condition during uninstall from ARP
always shows the fatal error message after displaying the launch condition
message.
Which leads me to your suggestion regarding the custom action
John Lalande wrote:
> What situations are they useful if they always show a Fatal Error
> dialog in ARP?
If you determine that you need some prerequisite to successfully uninstall.
> I am thinking of replacing the uninstall launch condition with a
> dialog that has a Retry button allowing the u
What situations are they useful if they always show a Fatal Error dialog in
ARP?
I don't want to skip the launch condition as I put it there. I don't want
users trying to uninstall while the program or Outlook are running because
it leaves files behind and this has been deemed unacceptable by ou
John Lalande wrote:
> In both cases I *do* get the launch condition error message. But with
> ARP uninstall, I receive an extra message indicating a fatal error.
Fair point. Yes, it's probably not MSI showing the error but ARP. MSI
returns 1603 to indicate that the launch condition failed, whic
Isn't this the same UI level as when I choose uninstall from the package's
context menu? Both methods of uninstall log this message:
"Client-side and UI is none or basic: Running entire install on the
server."
In both cases I *do* get the launch condition error message. But with ARP
uninstall
John Lalande wrote:
An interesting thought, but the LaunchCondition message *does*
display. The Fatal Error message appears after it is dismissed
Levi's right -- uninstall from ARP runs in "basic" UI mode. As there's
no authored UI (dialog boxes), the rule is that /some/ message
indicating f
An interesting thought, but the LaunchCondition message *does* display. The
Fatal Error message appears after it is dismissed
On 1/25/07, Levi Wilson <[EMAIL PROTECTED]> wrote:
This is a stab, but is it because when running from ARP it's running in
reduced UI, so it can't display a message box
This is a stab, but is it because when running from ARP it's running in
reduced UI, so it can't display a message box, and the fatal error is just
that the remove failed because the program was running?
On 1/25/07, John Lalande <[EMAIL PROTECTED]> wrote:
I have a LaunchCondition that with a cus
15 matches
Mail list logo
