When I install an msi, I am keeping a log like so: c:\>msiexec /i foo.msi /l* foo.log
The problems is that when I open foo.log, it turns out it's in UCS-2 Little Endian encoding. Chaning the encoding in .NET is trivial, but we have a legacy app that needs to append to the log file, and it's in VB6. I'm having quite a bit of trouble converting the file to ASCII from UCS-2 Little Endian. Without the conversion, the file gets mangled with garbage. Is there a particular reason why UCS-2 Little Endian is used to create the MSI log file? I don't think VB6 has the programmatic capacity to natively read such an encoding....I'm googling a solution now :-/ -- View this message in context: http://www.nabble.com/UCS-2-Little-Endian-encoding-of-MSI-Log-file-problem.-tf2292707.html#a6368349 Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
