Re: [WiX-users] using DUtil outside of windows installer projects

The Exit macros all use the "ExitTrace" macro. By default the ExitTrace macro maps to OutputDebugString(). You can #define ExitTrace before #include to change the behavior. For example, wcautil.h remaps the ExitTrace macro to WcaLogError function so all Exit messages are written to the the MSI lo

Re: [WiX-users] issue with the standardBootStrapper.rtfLicense theme file

Please file a bug. On Sat, Jan 8, 2011 at 2:29 AM, Sean Farrow wrote: > Hi: > There is currently an issue with the StandardBootStrapper.RtfLicense theme > file whereby it prevents keyboard only users accessing controls. > In short the TabStop element needs to be set to yes for all controls where

[WiX-users] using DUtil outside of windows installer projects

Hi: I'd like to use DUtil outside of Windows installer custom action projects. Where do the Exiton* and ExitWithLastError* functions write to? Are they reliant on someone using the WcaLog function? Regards Sean. -- Gaining

[WiX-users] using CaQuietExec in a defered custom action

Hi: I'm in the process of rewriting my installer custom actions to follow WiX best practices. I was previously using CAQuietExec and now have two questions: Can I reuse this from a custom action dll I write, or is it best to include all code in my own dll. And secondly, how do I determine the cos

[WiX-users] issue with the standardBootStrapper.rtfLicense theme file

Hi: There is currently an issue with the StandardBootStrapper.RtfLicense theme file whereby it prevents keyboard only users accessing controls. In short the TabStop element needs to be set to yes for all controls where a user is required to provide input. Any help appreciated. Regards Sean. -