Error log

[John]

Hi

How can I save a detailed error log in a file so that when my application
crashes the users can email me the log for investigation?

Thanks

Regards

[Hayato Iriumi]

Re: Error log

You may want to take a look at Microsoft's Exception Management Application
Block.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/emab-rm.asp

If that's a overkill, you can always write exceptions into text file or
write it into XML file or even database.

Try
' Your code
Catch exp As Exception
' Log the exception here
End Try

I would create a component that logs exception and call it from Catch block.

Good luck.

=============== =============
Hayato Iriumi (hayato@vbaspco der.com)
MCAD for .NET

[Fergus Cooney]

Re: Error log

Hi John,

|| How can I save a detailed error log in a file so that
|| when my application crashes the users can email me
|| the log for investigation?

<When> ?? <When> the application crashes ???

SCNR :-))

Regards,
Fergus

[Cor]

Re: Error log

John,
I think that when you want a detailled log that is availlable when the
program crashes, you have to close the file very often and reopen it
everytime.
I hopes this helps you on the route.
Cor

[Fergus Cooney]

Re: Error log

Hi John,

I have a proper answer for you this time. :-)

Windows provides a set of Event Log which it writes to when critical
events occur. It provides another for Applications to write to. Applications
can also create and write to their own. This last option is the route that I
recommend. Your customers can save the log to a text file and send it off to
you.

The logs can be examined from the Desktop menu:
Start/Programs/Administrative Tools/EventViewer. This will open the Management
Console for the Event Logs. From here you can explore the events or print the
whole lot out, etc. [There's no delete, though, as far as I can see. But you
may be able to delete them manually. Mine are in C:\WinNT\.Syste m32\config
(along with the Registry files).]

Creating and writing to the Logs is very easy in VB.NET as the Framework
provides an EventLog class. Here's a Module version but you could easily
create a class which inherits from EventLog.

Public Module ModuleEventLog
Public AppEventLog As New EventLog

Public Sub AppEventLog_Ini t
Const ksAppName As String = "appFooBar"
Const ksLogName As String = "FooBarLog"

'Register this application as being a source for the log
If Not EventLog.Source Exists (ksAppName) Then
EventLog.Create EventSource (ksAppName, ksLogName)
End If

AppEventLog.Sou rce = ksAppName
AppEventLog.Log = ksLogName
AppEventLog.Wri teEntry ("Starting") 'Optional
End Sub

Public Sub AppEventLog_Clo se
AppEventLog.Clo se
AppEventLog.Dis pose
End Sub
End Module

Initialise with:
AppEventLog_Ini t

Write to the Log with:
AppEventLog.Wri teEntry ("Merrily logging :-)")

Release with
AppEventLog_Clo se

Regards,
Fergus

[Fergus Cooney]

Re: Error log

Hi again John,

I've just discovered that you can examine the events logs using VS.NET by
opening the Server Explorer. You can also delete them from there.

Regards,
Fergus

[Cor]

OT: Re: Error log

Fergus,
I did eat my carrots again
[color=blue]
>How can I save a detailed error log in a file so that when my application
>crashes the users can email me the log for investigation?[/color]

I think using the system logs is not clever to use in an e-mail.
He beter can make his own file.
Even in the application that with a restart send the mail or an extra
application.
Cor

[Nice Chap]

Re: Error log

Have a Look at TraceListener

"John" <john@nospam.in fovis.co.uk> wrote in message
news:uRQr6U$eDH A.3104@TK2MSFTN GP11.phx.gbl...[color=blue]
> Hi
>
> How can I save a detailed error log in a file so that when my application
> crashes the users can email me the log for investigation?
>
> Thanks
>
> Regards
>
>[/color]

[Fergus Cooney]

Re: Re: Error log

Hi Cor,

|| He'd be better off making his own file.

You can use the system logs to make your own file. That's what my example
does. It uses the system's logging facility but has a log file of its own.
[Try it ;-)]

The trouble with writing your own log, as you pointed out, it that you
have to keep flushing it otherwise you lose the last block when you crash.
This won't occur when using the system logs because once the message is passed
it's out of your hands and you can merrily crash away.

|| Even in the application that with a restart send the
|| mail or an extra application.

It's entirely possible to read your event file and send it automatically.
:-)

Creating Event logs is easy and safe. That's why I recommend it.

Regards,
Fergus