Hi Robert,
there is a CustomAction that is executed at the beginning of the
InstallExecuteSequence and at the beginning of the InstallUISequence. It
is named "Shellextensionsdll5". This CustomAction sets the value of the
global property "ALLUSERS", if another product with the same UpgradeCode
is found. You find the code of this CustomAction in
setup_native/source/win32/customactions/shellextensions/upgrade.cxx
This CustomAction must be executed before the StandardAction
"FindRelatedProducts". Otherwise "FindRelatedProducts" does not work
correctly.
Regards
Ingo
Robert Vojta wrote:
On 3/24/07, Robert Vojta <[EMAIL PROTECTED]> wrote:
Hallo,
The problem here is, that I can't make it more verbose. I found just
one message - FindRelatedProduct -> no related products. Anyone know
if I can make it more verbose? To see what MSI checks, what compares,
...?
it looks like that I've found where the problem is. My setup.exe
starts in per-user mode (*) and can't detect per-machine
installations. When I install Sun's OO.o in per-user mode, my MSI
installer can detect installed OO.o
(*) I have no idea, why it starts in per-user mode. Sun's OO.o MSI
installer can detect per-user / per-machine installation, but my not.
I wonder why, because there is no change in the MSI installer in my
build when I compare it to Sun's OO.o.
Regards,
Robert
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
