You are asking the wrong guy (and probably the wrong newsgroup). I've never
gotten that deep into event log stuff. The most I've ever done is just
write strings and numbers for eventIDs and that has been all I've needed.
Maybe one of the platform sdk groups?
Joe K.
I'll try, meanwhile, can you tell me what have you don't? may be that's all
I need?! what do you mean by "write strings and numbers for eventIDs"?
TIA
"Joe Kaplan (MVP - ADSI)" <joseph.e.kaplan@removethis.accenture.com> wrote
> You are asking the wrong guy (and probably the wrong newsgroup). I've never
> gotten that deep into event log stuff. The most I've ever done is just
[quoted text clipped - 71 lines]
> >> >> >> >>> editing the Reg?! Can you share how, please?!
> >> >> >> >>> TIA
Joe Kaplan \(MVP - ADSI\) - 24 Jun 2005 14:51 GMT
Generally, what I do is this:
In a separate application run by the admin, do something that calls
EventLog.CreateEventSource like Dominick suggested. Sometimes this is a
simple app. Another easy way to do it is to have an EventLogInstaller class
in your assembly and have the admin run InstallUtil.exe on your assembly.
This will run the installer class and create the event source.
Then, from my code, I would have something that simply calls
EventLog.WriteEntry, passing in the source you created in the step above,
the message string, log type and eventID if I wanted to use event IDs.
That is generally enough to get this working. There are a variety of other
deployment options including MSI and creating your own message files, but
this will give you basic event log functionality.
HTH,
Joe K.
> I'll try, meanwhile, can you tell me what have you don't? may be that's
> all
[quoted text clipped - 90 lines]
>> >> >> >> >>> editing the Reg?! Can you share how, please?!
>> >> >> >> >>> TIA