On 3/23/07, Robert Vojta <[EMAIL PROTECTED]> wrote:
Hallo,
But I can't find, where is the place where OO.o MSI installer is checking for already installed OO.o. Anyone has an idea where I should look? Where is the code which is checking for already installed OO.o? Or is this done by MSI installer? If yes, how MSI installer does this? Based on the product name, product version, registry, ...?
for the mailing list archive purpose ... Each MSI installer package has its own ProductCode (GUID), which is unique. If you want to prepare MSI package for upgrades, ... you have to include UpgradeCode (GUID), which should be same for all OO.o versions = all MSI packages. MSI checks your UpgradeCode against already installed packages and you can customize actions in the Upgrade.idt file - what to do if newer package is installed, same or older. In my build, UpgradeCode is same as UpgradeCode in Sun's OO.o versions. When I install my 2.1 build, Sun's OO.o 2.0.4 build detects newer version properly. So, the UpgradeCode is correct. But when I install Sun's OO.o 2.1, 2.2, installed OO.o is not detected by my build. Strange. So, I found how to enable debugging of MSI installation. You have to add these two values to the system registry. HKLM/Software/Policies/Microsoft/Windows/Installer Debug = DWORD(00000007) Logging = STRING(warmupx!v) Then you can run DbMon.exe (from Platform SDK) and start your installation. Lot of debug messages are store in %TEMP%\MSIxxxxx.log. 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, ...? Regards, Robert -- Robert Vojta --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
