News and Change History

Version reference: 2.0.0 released on February 25th, 2017

If you are a registered user of our PHP compiler software ExeOutput for PHP 1.x, you should have received an email message with upgrade instructions. If not, please review our upgrade conditions.

To stay informed about future versions:

 ‌‌Follow us on Twitter.

 ‌‌Sign up for our RSS feeds.

 Download ExeOutput for PHP

Send Mail Sample - March 4th, 2017

We released another sample for ExeOutput for PHP based on PHPMailer that shows you how can create a console app (PHP in CLI mode) that sends emails.

WordPress and Adminer Samples - March 2nd, 2017

We released the first two samples for ExeOutput for PHP based on WordPress and Adminer. We also included a step-by-step guide for using WordPress and ExeOutput for PHP to make stand-alone desktop apps.

Version 2.0.0 - February 25th, 2017

  • Support for multiple versions of PHP: from 5.4 to 7.1. We still support Windows XP so we kept PHP 5.4, the last version that officially runs on this OS.
  • Chromium engine upgraded to Chromium Embedded Framework version 3 - Chromium version 51.0.2704.84 - CEF 3 branch 2704.1427, with multithreading support, offering an HTML5-compliant Web browser.
  • Ability to keep Windows XP compatibility for your applications: if the Rendering Engine's WindowsXPCompatible property is set to True, ExeOutput for PHP will use Chromium engine version 49 and CEF 3 branch 2623, the last ones that officially support Windows XP. Be sure to run the Web Update utility to download the Windows XP compatibility pack so that compilation files are available.
  • PHP CGI is now directly used as an external process contrary to the old SAPI method used in ExeOutput 1.x. This brings several advantages: PHP is separated from the UI process, giving more stability and responsiveness. If the PHP process crashes, a new one is started if you refresh the webpage. Your application itself doesn’t crash.
  • Full integration between PHP and Chromium rendering engine: AJAX, cookies, file upload and download dialog boxes, custom request and response HTTP headers, Developer Tools…
  • New console application (command-line or CLI applications) generation: you can turn PHP scripts into stand-alone EXE files without any PHP dependencies.
  • ExeOutput 2 still generates one single EXE file for distribution. Due to the size of the Chromium and PHP distributions, the EXE overhead’s size is near 30 MB.
  • New UI editor to create customized toolbars, menu bars, ribbons… Associate actions to controls, define their properties...
  • New skin engine and option not to use any skin at all (Windows look).
  • Better support for PHP frameworks such as Laravel, CodeIgniter, Fat-Free...
  • Can include a portable MySQL server (MariaDB) to work with your compiled PHP applications. The MySQL server is managed by the application itself without required user action.
  • Export to PDF option in addition to Print.
  • Support for OPCache and XDebug PHP extensions.
  • Windows UAC option: EXE files can now request administrative rights.
  • SHA256 code signing is supported for recent Windows versions.
  • Support for Paquet Builder 3 in order to make Setup packages.
  • Improved built-in PHP.INI editor, added search support.
  • ExeOutput for PHP 2 can now run complex PHP projects such as WordPress, phpmyadmin, Adminer and so on (contrary to ExeOutput 1.x).

Compatibility:

  • We dropped support for Trident engine. For Windows 10, Microsoft ended development of Internet Explorer and its associated Trident engine (except security fixes). Currently, they don’t provide a way to implement the same engine as Microsoft Edge in legacy Win32 applications. It is said this could change in the future. When importing an ExeOutput 1.x project, the engine is automatically set to Chromium.
  • Custom toolbar buttons and menus from ExeOutput 1.x projects can’t be imported in ExeOutput 2.
  • New skin engine: old skins are no more compatible. ExeOutput 2 comes with a new set of skins. A new skin editor is also available.
  • Dialog boxes in HTML format are automatically replaced.
  • Macros script has been removed.

A backup in Zip format with modified data is created in the same folder as the EXOP project file when you import an ExeOutput 1.x project.