#10 Can't convert InstallShield Dev 8 project to XML

closed
msi2xml (11)
5
2012-07-18
2004-03-01
legalize
No

InstallSUCK exports MSI projects to a bunch of .IDT
database text files.

This actually sucks for source code control when you
have multiple developers working on files because the
rows are always sorted by primary keys when the tables
are exported. This, in turn, confuses difference tools
because the resorting screws up their diff algorithms.

So I thought I would try out msi2xml on the InstallSUCK
project file (.ISM extension).

However, when I do this, msi2xml (current version) barfs
out on the InstallShield table with the message "Failed
to convert MSI file!"

I've attached and InstallSUCK project that reproduces
this problem along with the text output from msi2xml.

Discussion

  • legalize

    legalize - 2004-03-01

    Logged In: YES
    user_id=36316

    OK, it wouldn't let me attach the ZIP file because it was
    680K. You can get it from

    http://www.xmission.com/~legalize/msi/error.zip

     
  • Daniel Gehriger

    Daniel Gehriger - 2004-03-02

    Logged In: YES
    user_id=30009

    The error happens because they are storing the ASCII control
    code 0x01 in a string field.

    I'll detect such (rather unexpected) characters and encode
    them. Update to follow.

     
  • Daniel Gehriger

    Daniel Gehriger - 2007-09-26

    Logged In: YES
    user_id=30009
    Originator: NO

    Better late than never...

    Even Orca crashes when loading this file. Anyway, I catch the exception and issue a warning.

     


Anonymous

Cancel  Add attachments





Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks