title: Create EventLog source in WiX without an event message file
body: <p>I've seen a few questions <a href="https://stackoverflow.com/questions/58538/how-do-you-create-an-event-log-source-using-wix">here</a> and <a href="https://stackoverflow.com/questions/3590015/wix-create-eventsource-using-net-message-file">there</a> about creating event log sources using WiX. What puzzles me is why <code>util:EventSource/@EventMessageFile</code> is required. It's annoying having to specify it when you don't need a message file to write event log entries, and the abstraction offered by .NET's <code>System.Diagnostics.Trace</code> doesn't expose the ability to use one.</p>
  
  <p>The standard advice seems to be to use a directory search to set the attribute to the <strong>Framework's</strong> <code>EventLogMessages.dll</code>, but nobody repeating this mantra ever gives any justification for it. </p>
  
  <p>Short of not using the (tested, robust) custom actions supplied with WiX, is there any way to get around this requirement?</p>
  
  <p>And why do authors of managed applications which don't use this aspect of the event log take such pains to (apparently) pointlessly refer to a Framework DLL rather than one of their own executables?</p>