Hi Users, I am working on a product that needs to support Windows 7 w/ UAC enabled. The MSI has a few custom actions that perform various configuration items that I would like to keep contained within the MSI/product install.
The custom actions are Execute='deferred' with Impersonate='no' and they are scheduled Before='InstallFinalize'. One action is a vb script, and the other calls a native C/C++ dll. They *both* contain configuration items that require elevated privileges. Now, I have verified that the vb script action works fine, however the dll custom action does not. I am getting a permission error from the dll custom action when it runs. So, it appears to me that there is a difference in the two different types of custom actions, and how the user/system privileges are propagated from the msiexec process to these action processes. I've done some digging online (and will continue to) regarding the issue, but have not run across this particular case with the different action types acting differently. I am running the MSI on a Win7 x32 system with UAC using WiX 3.0.5419. As always, thanks for the help. ------------------------------------------------------------------------------ Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
