Requesting Additions to the Vendor Patch Module - Foxit PDF Reader (EXE variant)

[ng_kai_long]

• Product Name (including vendor name)  Foxit PDF Reader (EXE variant)
• Product Version (the latest available) 12.1.2.15332
• Comments (any optional information you believe will help the request) - Only MSI variant available in VPM but EXE version is the one that is easily obtain by end user via the vendor page.
• Download URL (where it be downloaded) - PDF Software Free Download | Foxit Software
• Information URL (product home page) PDF Software & Tools Tailored to Your Business | Foxit
  Foxit PDF Reader EXE Installer Public Properties – Help Center | Foxit Software

[bkelly · Accepted solution]

We include the MSI, so there should be no need to download either manually. We always choose to offer the MSI over the EXE because of the deployment benefits such has over legacy setups. Is there something about the EXE that provides any unique benefit we should consider?

[ng_kai_long]

The reason behind the request is that the EXE version is the one easily available on vendor's webpage which this is how a normal end user would then be getting. MSI installer is not as easily available.
We understand the use of MSI because of the benefits but the MSI deployment or use case would not replace the existing EXE installation as part of the patching requirements. It would only the create a separate instance (computer will then have EXE and MSI installation together) within the computer hence more work for administrator to patch and manage.

Hope this clarifies the scenarios.

[bkelly]

Good news: if you add the Public Property REMOVEGAREADER=1 to the MSI command line, the PDFReader Desktop version (the .exe version) will be uninstalled so you can effectively patch the exe version with the msi.