#68 Unable to detect MSI install for some applications

[Jim Lutz]

Some applications use some version of their name instead of a GUID for their Produce Code when they are installed, despite specifying the Product Code is specified with XML in the update package, but LUP won't accept anything but a GUID for MSI Install detection. As a result, MSI detection is effectively broken for these applications. Can we get an option for MSI detection that is not based on a GUID? It is possible to detect the registry key directly, but I consider that an undesirable workaround.

[Bryan Dam]

Can you give me an example app installer to test with? I'll look into it but I suspect that the package metadata requires a GUID and won't validate if we stick text into it.

[Jim Lutz]

Notepad++ is one that you can try with. It uses Notepad++ for the key instead of a GUID.

Sent from my iPhone

On Nov 18, 2015, at 7:03 PM, Bryan Dam bryandam@users.sf.net wrote:

Can you give me an example app installer to test with? I'll look into it but I suspect that the package metadata requires a GUID and won't validate if we stick text into it.

[bugs:#68] Unable to detect MSI install for some applications

Status: open
Group: v1.0_(example)
Created: Wed Nov 18, 2015 03:53 PM UTC by Jim Lutz
Last Updated: Wed Nov 18, 2015 03:53 PM UTC
Owner: nobody

Some applications use some version of their name instead of a GUID for their Produce Code when they are installed, despite specifying the Product Code is specified with XML in the update package, but LUP won't accept anything but a GUID for MSI Install detection. As a result, MSI detection is effectively broken for these applications. Can we get an option for MSI detection that is not based on a GUID? It is possible to detect the registry key directly, but I consider that an undesirable workaround.

Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/localupdatepubl/bugs/68/

To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/