Microsoft DotNet
12/13/2002 8:23:00 AM
If anyone would like, I have an EventLog class that extends the one provided
with .NET to include sources, message file manipulation and so forth.
Handles writing parameters & byte data to the event log as well. Comes w/ a
fairly rough message compiler that I wrote as well - if you'd like it, you
can email me @ nsmith_removethissoidontgetspammed@insario.com
"Richard Grimes [MVP]" <richardg@mvps.org> wrote in message
news:#jWRIfUoCHA.2360@TK2MSFTNGP09...
> Nicholas,
>
> By all means do use message resource files, the way that EventLog creates
> messages is _really_ bad and IMHO should never have been allowed to get
out
> of the beta. Effectively .NET did just what VB6 did and that was bad. The
> tool you need is mc.exe you can get it with the Platform SDK or with
VC.NET.
> Perhaps if enough people continue to use this rather than the lame excuse
in
> EventLog Microsoft might fix EventLog.
>
> Richard
>
> "Nicholas A. Piazza" <npiazza1@san.rr.com> wrote in message
> news:641501c27642$fe588b50$3bef2ecf@TKMSFTNGXA10...
> > Prior to .NET it was possible to create
> > eventmessagefile.dll and categorymessagefile.dll for use
> > in event logging by creating a .MC text file and compiling
> > it with the Message Compiler utility. What is the
> > approved .NET way of accomplishing the same thing? I have
> > looked at all of the EventLog related classes, and
> > although there are methods (or properties) to get
> > information such as Event Id, Category Id, Category
> > String, and insertion strings, I could find no way of
> > creating the appropriate file and associating it with an
> > event log file and source.
>
>