tag:blogger.com,1999:blog-9537945.post1966200424480991034..comments2023-08-20T04:16:39.520-05:00Comments on Deployment Engineering Archive: In Defense of Merge ModulesChristopher Painterhttp://www.blogger.com/profile/12167478740431444267noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-9537945.post-29662121438099465932010-09-15T23:08:05.459-05:002010-09-15T23:08:05.459-05:00Yup, those are the ugly MS MSM's I talked abou...Yup, those are the ugly MS MSM's I talked about.<br /><br />To be honest I've only briefly dove into localization. My investigations lead me to believe that WiX and InstallShield are both lacking in terms of what the MSI SDK says should be possible.<br /><br />I'd love to be able to make multilanguage MSM's and then aggregate them up into a single multilanguage MSI.<br /><br />Christopher Painterhttps://www.blogger.com/profile/12167478740431444267noreply@blogger.comtag:blogger.com,1999:blog-9537945.post-79186066944482302392010-09-13T11:17:20.869-05:002010-09-13T11:17:20.869-05:00I author merge modules for use internally only. M...I author merge modules for use internally only. My biggest complaint is with using InstallShield to author merge modules. If you have a multi-language MSI installation, using InstallShield to author the modules is next to useless. IS doesn't support creating standard multi-language merge modules (with multiple langage CABs embedded in the module). The first thing I tried was separating Colby Ringeisenhttps://www.blogger.com/profile/08696301684260588101noreply@blogger.com