>What about contributing a simple-minded EventLog implementation?

I've already done a first EventLog implementation, if anyone is interested.

This implementation does absolutly nothing, but it compiles and run without
any (known) errors.
Only 14 methods/properties are still missing to EventLog be fully
operational :
* EventLog: LogDisplayName
* EventLog: Clear()
* EventLog: Close()
* EventLog: void WriteEntry(string source, string message, EventLogEntryType
type, int eventID, short category, byte[] rawData)
* EventLog: EventLog[] GetEventLogs(string machineName)
* EventLog: string LogNameFromSourceName(string source, string machineName)
* EventLog: bool Exists(string logName, string machineName)
* EventLog: void Delete(string logName, string machineName)
* EventLog: void CreateEventSource(string source, string logName, string
machineName)
* EventLog: bool SourceExists(string source, string machineName)
* EventLog: void DeleteEventSource(string source, string machineName)
* EventLogEntryCollection: EventLogEntryCollection(string logName, string
machineName)
* EventLogEntry: void GetObjectData(SerializationInfo info, StreamingContext
context)
* EventLogEntry: void Fill()

Herv�

PS: in attached files, 2 completed files (EventLog.cs and EventLogEntry.cs)
and a patch for EventLogEntryCollection.
PS2: as Gert Driesen said, "What direction should we take on unix ?"

Attachment: EventLogEntryCollection.patch
Description: Binary data

Attachment: EventLogEntry.cs
Description: Binary data

Attachment: EventLog.cs
Description: Binary data

Reply via email to