I'd like to stay away from using the Windows Event logging.  The true goal
is to be able to support external clients without requiring us to connect to
their networks to retrieve our logs.

For an internal app this does sound like an interesting idea.  What kind of
system would you use to keep an eye on Windows Event logs on computers in a
network?

Thanks,

Shane

On 4/5/07, Adwait Ullal <[EMAIL PROTECTED]> wrote:

If you're within a corporate network, you might want to consider logging
it
to the Windows Event log so that your Enterprise Management systems can
monitor those logs and alert you of the problems.

Hope that helps (though I did not answer your exact question).

- Adwait

--
Adwait Ullal

e: mailto:[EMAIL PROTECTED]
w: http://www.adwait.com
l: http://www.linkedin.com/in/adwait
j: http://finance.groups.yahoo.com/group/AdwaitsDotNetJobs

On 4/5/07, Shane Courtrille <[EMAIL PROTECTED]> wrote:
>
> I'm working on a small test smart client application.   My next step is
to
> try to implement logging so that if a client has a problem I can get
> details
> on it.  I'm using the log4net framework so I have a lot of options as to
> how
> to log.  My first thought is to try logging to file and providing the
user
> with the location of the file.
>
> Does anyone have any guidelines on logging from a smart client?  I've
> looked
> around for guidelines for saving files from a smart client and haven't
> seen
> anything.
>
> Thanks,
>
> Shane
>
> ===================================
> This list is hosted by DevelopMentor(r)  http://www.develop.com
>
> View archives and manage your subscription(s) at
> http://discuss.develop.com
>

===================================
This list is hosted by DevelopMentor(r)  http://www.develop.com

View archives and manage your subscription(s) at
http://discuss.develop.com


===================================
This list is hosted by DevelopMentorĀ®  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com

Reply via email to