Re: Development of event log message file
- From: Mr Major Thorburn <MrMajorThorburn@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 6 Sep 2007 00:36:00 -0700
Steve, the reason the event error message has the reference to a lack of
registry info is because the Application entry in the registry for the
EventLog Service does not have a key for an EventMessageFile. If I develop a
mesage file using the rudementory tools from older Visual Studios and create
the registry key pointing to the created DLL I can resolve the message
problem.
The original reason for the post was to ask if there was a better way for
developing EventLog Message Files.
Regards, Major.
"Stevanich" wrote:
Major,.
To read the event log on a remote computer, which is what it sounds like you
are trying to do, use the System.Diagnostics namespace.
The EventLog class has a constructor that takes two string parameters. The
first is the name of the event log to read, the second is the name of the
machine to open the event log on. Make sure the user running the program
has rights to read the remote event log.
Hope this helps,
Steve
"Mr Major Thorburn" <MrMajorThorburn@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:99EB27C5-4321-44B9-88A4-317E7977D3AD@xxxxxxxxxxxxxxxx
The reason I am interested in the messagefile is because we get the
following
in the event log entries
The description for Event ID (0) in Source (application) cannot be found.
The local computer may not have the necessary registry information or
message
DLL files to display message from a remote computer. You may be able to
use
the /AUXSOURCE= flag to retrieve this description; see Help and Support
for
details.
I would like to eliminate this if at all possible.
Regards, Major.
"Stevanich" wrote:
Major,
We don't. The code in the link I referenced does it for us. Why are you
concerned with the physical file?
Thanks,
Steve - dotneticated.com
"Mr Major Thorburn" <MrMajorThorburn@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:AECF8E78-C651-4016-9354-1114C1F973DE@xxxxxxxxxxxxxxxx
Thanks, I read that article.
The reason for the post was to find out how the current developers of
ASP.
NET applications who use global.asax to create event log entries manage
to
develop the associated eventlog message file when using Visual Studio
2005.
I have managed to develop a messagefile using the cobbled together set
of
tools.
It just seemed to me to be a bit of a botch and wondered if there a
better
way.
Regards, Major.
"Stevanich" wrote:
Major,
Are you just looking to write to a new section in the event log? You
can
do
this without any of the legacy stuff.
http://support.microsoft.com/kb/307024
Hope this helps,
Steve - dotneticated.com
"Mr Major Thorburn" <MrMajorThorburn@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
in
message news:2554F0A6-BB87-46DF-BEFC-BE5E814BD08F@xxxxxxxxxxxxxxxx
Anyone have any hints on how I may proceed in developing an event
log
message
file for my .NET 2.0 web application?
I have read artcles for doing this sort of thing that use .mc files
and
mc.exe to produce a .rc file, rc.exe to produce a .res file and
link.exe
to
create a dll but these are all old VC98, VB98 tools and not part of
VC
2005.
How do I do this using VC 2005?
Regards, Major.
p.s. Major is my Christian name ;-)
- References:
- Re: Development of event log message file
- From: Stevanich
- Re: Development of event log message file
- From: Mr Major Thorburn
- Re: Development of event log message file
- From: Stevanich
- Re: Development of event log message file
- Prev by Date: RE: How to give conditional parameter input on datatable Insert
- Next by Date: Re: Launch .bat file from IDE?
- Previous by thread: Re: Development of event log message file
- Next by thread: Re: XML Comments in code-beside files
- Index(es):
Relevant Pages
|
