MSI2XML / XML2MSI / News: Recent posts

This new release fixes all open bugs that have been reported over the past two years.

It also provides improved error reporting and color-coded messages.

This new release uses MSXML version 6.0 or later. MSXML 6.0 is not included in the msi2xml setup. You probably already have it on your computer if you have the .NET Framework 2.0 or Windows Vista. Otherwise, you can download it from the Microsoft web site.

Added new switch "-s" to xml2msi to set / add properties in the Property table.

Release 2.1.8 adds a new switch "-m" to msi2xml to support merge modules.

• fixed date formatting error resulting in "Failed to convert the MSI database!" error message

Version 2.1.0 adds tons of new options. I really needs someone to write some nice docs...

Any volunteers ?

Version 2.0 adds extraction and compression of cabinet files.

A Windows Installer Database To XML Bi-Directional Converter. The command line tool msi2xml converts Windows Installer Databases (.msi) to text based XML files. The complementary tool xml2msi reconstructs the .msi from the XML file.

• md5 formatting bug fix
• Win9x unicode support

Cosmetic fixes (see Change Log)

• Fixed syntax error in xml-stylesheet PI
• Updated to MSXML 4.0
• Created VC.NET project files
• Put #import statement in conditional clause, to allow for compilation with gcc.

Codepage aware, uses MSXML 4.0, many improvements.

A Windows Installer Database To XML Bi-Directional Converter. The command line tool msi2xml converts Windows Installer Databases (.msi) to text based XML files. The complementary tool xml2msi reconstructs the .msi from the XML file.

This version fixes invalid character in _Streams table.

Release 1.2.0 adds the following features:

• new "-p" option to specify prefix path to xml2msi

• export of unreferenced binary streams fixed.