Greetings, I have a question regarding embedding transforms (.mst) into a single MSI. I realize this is more of a Microsoft question, but am hoping there are some MSI ninja's here who might be able to help provide an answer. Question: Does MSI (Microsoft) formally support embedding language specific transforms (.mst) into a single msi installer? I realize this can be done, but based on my google-foo it's not clear if this is truly proper/supported. More info: I'm using a basic MSI project with InstallShield 2012 Spring to produce a single (english based) msi installer. As part of the build I also produce a set of language non-english transforms (.mst) which can be applied to the msi using the misexec TRASNFORMS property. However what I really want to do is produce a single msi which embeds the transforms so that I don't need to tote around all the mst files for multi-lang support. I've used the WiSubStg.vbs and WiLangId.vbs commands to embed the transforms into my msi (post InstallShield build) and things appear to be working. However I'm concerned if this approach is supported/proper. In my searching I found a number of sites which state this approach is not formally supported by MSI, but those posts where years old and I've since seen posts that the MSI technology has made advancements in this area. Moreover I see the Windows dev center discussing embedded transforms formally which leads me to believe the approach supported. BTW -- My target platform has: Windows ® Installer. V 5.0.9200.16384 Resources: http://msdn.microsoft.com/en-us/library/windows/desktop/aa368347(v=vs.85).aspx http://www.installsite.org/pages/en/msi/articles/embeddedlang/ http://go4answers.webhost4life.com/Example/multiple-language-setup-package-213354.aspx Thanks ... View more

Greetings, I'm using IS 2012 Spring, and I have a 'main' basic MSI project. As part of our development effort we're using DIM projects to help coordinate multi-developer efforts. In our environment we have a main (Basic MSI) project which will reference other DIM projects. The DIM projects contain (among other things) Dialogs. In the DIM project (just taking a generic example here) I have a new dialog which provides a 'next' and 'back' button. I've configured the 'Next' and 'Back' button behavior to emit a 'NewDialog' event where the argument is the next/previous panel so show (respectively) and the condition is 1 (i.e. always). For example in the DIM I have MyDIMDialog with behavior: ControlName "Back" Event "NewDialog" Argument "APreviousPanelFromMainProject" Condition "1" ControlName "Next" Event "NewDialog" Argument "ReadyToInstall" Condition "1" Based on the above MyDIMDialog is the last panel before the 'ready to install' built-in. In the main (Basic MSI) project I've referenced the DIM module and associated it with a feature. I've configured the dialogs in the main project such that "APreviousPanelFromMainProject" has its NewDialog event with an Argument of the referenced DIM dialog (the generate Dialogs name). Sidenote -- I'm trying to sequence the referenced dialog in of existing UI dialogs -- not as a "top level" UI sequence dialog like the built-in "Patch Welcome". However when I build and run the MSI (we are using MSI not setup.exe) and I get to the APreviousPanelFromMainProject panel, clicking next does nothing -- the panel just flashes a little but does not proceed to my imported DIM dialog as sequenced. I've also tried configuring the APreviousPanelFromMainProject such that its NewDialog event for 'next' has an argument of "MyDIMDialog" (i.e. I don't use the generated referenced dialog name which is of the form MyDIMDialog.XXXXXXXX_XXXX...). In this case when I run the installer I get an error "Error 2803. Dialog View did not find a record for the dialog MyDIMDialog". So the question comes down to --> How do sequence a DIM referenced dialog in a basic MSI project? My google-foo has not helped solve this issue so hoping someone here can help. Thanks ... View more