I'm assuming your custom installer is an installer class custom action, and
you're calling it during the install as an Install custom action. If so, the
Installed. The custom action then won't get called if the product is already
installed.
"Alexander Groß" <PLEASEAlexanderGrossREMOVETHIS@gmx.de> wrote in message
news:%23vjj7c8ZFHA.2940@tk2msftngp13.phx.gbl...
> Hi Phil,
>
> thanks for your quick reply.
>
> Phil Wilson <Phil.Wilson@unisys.spamcom> wrote:
> | The repair is calling your custom action again, and those properties
> | are all undefined, so I assume that your code is overwriting those
> | install-time values with empty values.
>
> Yes, the debugger shows that the stateSaver collection is empty (or at
> least
> not containing the values I set on first install) at the start of
> MyInstaller.Install() when doing a repair. I don't overwrite the
> stateSaver
> values because I've got no idea where to get them from. I've implemented a
> way to exit Install() immediately when a repair install is triggered. It
> seems as the MSI runtime decides to throw my persisted values away as the
> repair's stateSaver is empty. Not sure if this works as it should. Or am I
> doing wrong?
>
> | A condition of Not Installed
> | on your custom action should help (Installed is case sensitive - it's
> | a property that is set if your product is already installed).
>
> I am not quite sure what you mean here. As far as I've read in the docs
> I've
> got no way to set properties in my .NET code. Do I?
>
> Again, thanks for your help - I am new to MSI and haven't found a good
> overview on the subject. Any recommendations?
>
> Best regards,
>
> Alex
>
> --
> _______________________________________
>
> Alexander Groß
> Dipl.-Ing. (BA) für Informationstechnik
> PLEASEAlexanderGrossREMOVETHIS@gmx.de
>
http://www.it99.org/axl > ICQ# 36765668
> _______________________________________
>
>