Bob, you are my hero. :) Here is a WiX fragment produced by tallow of a registry dump of a custom event log and two sources that were produced by a .NET installer class run against the .NET 1.0 from a fairly old VS.NET install project I used in the past with names sanitized:
<Wix xmlns="http://schemas.microsoft.com/wix/2003/01/wi";> <Fragment> <Registry Root="HKLM" Key="SYSTEM\CurrentControlSet\Services\Eventlog\Auth Module"> <Registry Name="Sources" Value="AuthorizationModule[~]Auth Module[~][~]" Type="multiString" /> </Registry> <Registry Root="HKLM" Key="SYSTEM\CurrentControlSet\Services\Eventlog\Auth Module\AuthorizationModule"> <Registry Name="EventMessageFile" Value="C:\\WINDOWS\\Microsoft.NET\\Framework\\v1.0.3705\\EventLogMessages.dll" Type="string" /> </Registry> <Registry Root="HKLM" Key="SYSTEM\CurrentControlSet\Services\Eventlog\Auth Module\Auth Module"> <Registry Name="EventMessageFile" Value="C:\\WINDOWS\\Microsoft.NET\\Framework\\v1.0.3705\\EventLogMessages.dll" Type="string" /> </Registry> </Fragment> </Wix> The .NET event source message DLL has the same name in each version of the framework and is probably interchangeable, but you'd probably want some reasonaable way to substitute in the path there. In .NET 2.0, there are more options on the EventLogInstaller class create more full-featured event logs. .NET 1.0 and 1.1 were pretty sparse and missed some core features. Are you planning to add some authoring for custom logs as well as sources? That too would be great! I haven't used WiX 3.0 yet (still using 2.0; was waiting for the green light from Derek), but I'll definitely check this out in the latest build and tell you what I think! It may take a few days. Joe K. ----- Original Message ----- From: "Bob Arnson" <[EMAIL PROTECTED]> To: "Joe Kaplan" <[EMAIL PROTECTED]> Cc: "Eric Fesh" <[EMAIL PROTECTED]>; <wix-users@lists.sourceforge.net> Sent: Friday, August 25, 2006 9:45 PM Subject: Re: [WiX-users] InstallUtil considered harmful... What next? > Joe Kaplan wrote: >> There is a gotcha though with the managed service installer classes. Not >> only does it create a service in the service database, but it also >> installs an event source for you in the application log for the service >> to write to. In order to support this behavior, you'll need to create >> some WiX authoring to create an Event Source. This is done by setting >> the proper registry elements in HKLM to create an Event Source. >> > Interestingly, this week's release of WiX v3 (3.0.2023.0) includes this > note in history.txt: > > BobArnso: Add EventSource strongly-typed authoring to WixUtilExtension > > Very new, so any feedback would be appreciated. >> There is another trick to be aware though, in that .NET event sources use >> the message DLL that comes with the .NET framework, and the registry will >> contain a path to that. You may need to make that dynamic based on the >> version of the .NET framework you are supporting. It could get a little >> tricky, but should not be too hard. >> > Could you post what your registry looks like with that? I wasn't able to > find any examples of managed event sources on any of my dev machines. > > -- > sig://boB > http://bobs.org > ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
