I would not try to redeploy dism.exe from one pc to another, as that can definitely cause problems. I have read in MSDN dismapi docs, that dism.exe is specific the OS, which it was deployed as a part of. As far as I know there is no redistribution license. I do not think that trying to do the equivalent of a Custom Action in the ExePackage is the intended use.
You can call dism.exe in a Custom Action (or call the dism api). An issue that you will run into (which may also be a factor in what you tried) is related to platform bitness. You need to create two MSI packages (x86 and x64) which each call a x64 or win32 (for C++) Custom Action, which interacts with the correct path to the correct version of dism.exe (x86 or x64). I think you can search the forum and find some examples. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-use-dism-exe-in-WiX-ExePackage-for-IIS-feature-activation-tp7598913p7598915.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
