I think you can, but it takes some tinkering. In the merge module project, you'll need to add the ActionText table in the Direct Editor view (either export from another project and import into the MSM project, or manually create the table with Action, Description, and Template columns of types s72, L64, and L128). In the new ActionText table, put this into the Action column--- ActionName.HHHHHHHH_HHHH_HHHH_etc. ---where ActionName is the action name in the Custom Actions view, and HHHHHHHH_etc. is the Module ID GUID value from the General Information view. The Description column takes the text you want to display: "Now running merge module action..." After adding the merge module to your installer project, the action's text should appear at the usual time. Normal conditions apply: must be deferred action, etc. ... View more

Thanks..... ... View more

If the file is the keyfile of a component, the MsiGetComponentPath API can be used to obtain the full path to the file including the filename. You can also use MsiGetProperty (for example, if the file installs to INSTALLDIR) to get the value of the path the file installs to, then append the file name to this path. ... View more

Holger_G wrote: Your custom action should be a Deferred Execution in System Context. . What about the CAs that cannot be deferred? ... View more

I did something similar, but in our case, we wanted the product name to reflect its 64-bitness, so in the Product Configuration screen I changed the name of the 64-bit product to My Product's Name (x64). This allowed me to test for VersionNT64 And Not (ProductName >> "(x64)"), but I think I like Michael's approach better. ... View more

It just has to be a custom action, so the Standard DLL custom action will work fine. There are some limitations to what a custom action can do when run from a Control Event, mostly with regards to logging, but I'm not aware of any limitations on the action type. ... View more

OK, thanks, I think it is worth escalating this to IS development team as one might need to use OR. What is the proper process to report bugs/enhancements etc? Thanks! ... View more

Re-sending.. ... View more

Re-sending.. ... View more

Ok thanks! ... View more

The installer evaluates conditions at the cost finalize action. The UI runs before that. So you haven't got a sequencing issue, you more likely have a condition issue. What you need to test is the appearance or dissapearance of the property for a checkbox. A lot of people make the mistake of checking true/false or 1 and 0 etc. If your check box property is called MYPROPERTY, your condition for checked is simply: MYPROPERTY or to test for unchecked then you want: Not MYPROPERTY To default the check box to checked then add the property with any value to your property table. To default the check box to unchecked then delete the property Hope this helps ... View more

The Releases > Release Media > Build tab has an option called 'Languages Dialog' that pops up a language chooser before the installer starts. ... View more

Thanks for the pointer, Robert.. Anyone looking into this can take a look at the links below: http://msdn.microsoft.com/en-us/library/aa368281(VS.85).aspx http://msdn.microsoft.com/en-us/library/aa369487(VS.85).aspx ... View more

Hi, I am also facing the same problem, like, if I do any changes into the Filters.xml and those changes is not get reflected in the build which was created by "IS 12 Standalone." Do you found any solution for this? If yes, please let me know. Thank You! Regards I.Muthuraja ... View more

(Follow-up of sorts [post=442345]here[/post]...) ... View more