Reggie Burnett wrote:
> BTW, are there any suggested ways of detecting that a CA has failed
> and showing a nice error message to the user instead of 'Error :
> a program has failed to complete' type of message?
In a DLL CA, you can use something like MsiProcessMessage to show a
custom err
I see my mistake. I had mistakenly scheduled the CA after InstallFinalize.
BTW, are there any suggested ways of detecting that a CA has failed and
showing a nice error message to the user instead of 'Error : a program
has failed to complete' type of message?
On 8/21/07, Bob Arnson <[EMAIL P
Reggie Burnett wrote:
> That explains it. However, it's still contradictory to users when the
> installer clearly tells them that no changes have been made to their
> system and that is a lie. :)
It's true as long as you don't run custom actions after the install's
finished. MSI will undo wha
On 8/20/07, Bob Arnson <[EMAIL PROTECTED]> wrote:
>
> Please keep *wix-users* on the thread.
>
Oops. I hit reply instead of reply all. Sorry
Reggie Burnett wrote:
>
> Sure. However, what didn't roll back was not a custom action. A custom
> action failed and it was a GAC registration that did
Please keep /wix-users/ on the thread.
Reggie Burnett wrote:
Sure. However, what didn't roll back was not a custom action. A
custom action failed and it was a GAC registration that didn't roll back.
If you use MSI GAC support, assemblies aren't installed to the GAC until
after the installat
Reggie Burnett wrote:
> I have a Wix authored install that is very simple. It installs a .NET
> assembly into the GAC and also into a folder and then attempts to run
> installutil on the assembly in the folder. THe installutil run
> failed due to some directly problem (I think). The installe
6 matches
Mail list logo
