All,
There is a KB article pertaining to windows installer running every time an
application starts - so I know it's an issue - but the KB article pertains to
MS Office only.
I am seeing the same behavior as the MS Office installer issue in my
installer package. The behavior started happening after I added a custom
installer step (implemented in C#) and the behavior stops if I remove my
custom installer step.
In my C# installer class implementation I overrode and implemented the
Install(IDictionay stateSaver) method only. I looked at the other methods
and events in the Installer class and I didn't see anything else that I
needed to do. Did I miss a step? How does the Installer know that my custom
step succeeded/failed - I almost get the feeling that the problem is
occurring because I am not signalling a succesful completion? Does anybody
have a clue how I can get around this problem?
Thanx in advance for your help...
