Has anyone any experience of this kind of thing? I've got an MSI with ProductLanguage property set to 1033, likewise the Languages field of the Summary Information is set to 1033. I have created a French transform (just for the dialog strings, for testing purposses) and called it 1036.mst and imbedded it into my MSI using msidb.exe. They say, all you need to do is run it and it'll compare the system locale with your embedded transforms and it'll all work - well, it doesn't.
You can call the embedded transform via command line by adding a colon into the sting: msiexec /i "<msi_path>" transforms=:1036.mst This DOES work. I decided that perhaps if I added 1036 to the Languages field of the Summary Information it'd work (now "1033,1036"). This gets me one step closer, as I get an error: "Error applying transforms. Verify that the specified transform paths are valid." and the package fails to get to the Welcome dialog. Running the same command line string with this additional Language in the Summary Information generates the same error message, albeit with curiously different formatting. So, I can run a package with an embedded transform from commandline, but as soon as I do what I thing is neccessary for the process to automate, it all fails. Clearly there is another step I need to complete before I get the desired behaviour. Any ideas? Many thanks, Gareth -- View this message in context: http://www.nabble.com/Embedded-locale-transforms-tf4523004.html#a12903192 Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
