It is a great undertaking, but I can't find anything knew in there, that I
can't already find on MSDN.
On a more constructive note.
Event log section fails to mention that code must be running as a member of
Administrators group for it to create Event log source. This is especially
important for code like the following sample parts to work:
....
if (EventLog.SourceExists(sourceName))
{
EventLog.DeleteEventSource(sourceName);
EventLog.Delete(logName);
}
....
if (!EventLog.SourceExists(sourceName))
{
EventLog.CreateEventSource(sourceName, logName);
....
Administrator membership is also a reason for installer to create event log
sources and performance counters instead of doing it from the main
application.
Performance counters section is weak. A not so obvious problem of counting
time span is not covered at all and it is part of many performance counters.
AverageTimer32 example could be quite valuable.
Multi-instance performance counters can easily run out of memory.
Interesting topic...
[quoted text, click to view] "Richard Grimes [MVP]" <richardg@mvps.org> wrote in message
news:%23KSq%23PseHHA.4772@TK2MSFTNGP05.phx.gbl...
> New, free, .NET workshop from Richard Grimes, covering Conditional Code,
> Tracing, Asserts, .NET Trace Sources and Trace Listeners, Performance
> Counters and the Event Log:
>
>
http://www.grimes.demon.co.uk/workshops/instrumentationWS.htm
>
> Richard
> --
> Free .NET tutorials,
> Fusion:
http://www.grimes.demon.co.uk/workshops/fusionWS.htm
> Security:
http://www.grimes.demon.co.uk/workshops/securityWS.htm
> Instrumentation:
>
http://www.grimes.demon.co.uk/workshops/instrumentationWS.htm
>
>
>
[quoted text, click to view] bazad wrote:
> It is a great undertaking, but I can't find anything knew in there,
> that I can't already find on MSDN.
That's not the point. It's for people who don't want to trawl through
MSDN.
If you go on any training session you'll get stuff that is readily
available in MSDN too, and yet people are willing to pay for those ;-)
[quoted text, click to view] > On a more constructive note.
>
> Event log section fails to mention that code must be running as a
> member of Administrators group for it to create Event log source.
It should, and I thought it did, but it doesn't. I'll change it.
[quoted text, click to view] > Administrator membership is also a reason for installer to create
> event log sources and performance counters instead of doing it from
> the main application.
>
> Performance counters section is weak. A not so obvious problem of
> counting time span is not covered at all and it is part of many
> performance counters. AverageTimer32 example could be quite valuable.
Don't worry, that's already taken care of, it's just that I haven't
posted it yet.
[quoted text, click to view] > Multi-instance performance counters can easily run out of memory.
> Interesting topic...
Indeed.
Richard
--
Free .NET tutorials,
Fusion:
http://www.grimes.demon.co.uk/workshops/fusionWS.htm
Security:
http://www.grimes.demon.co.uk/workshops/securityWS.htm
Instrumentation:
http://www.grimes.demon.co.uk/workshops/instrumentationWS.htm