At my current client we use the MS Enterprise Library logging block, but Log4Net has probably just as many options for logging. For the smart clients we have exposed a web service on an internal web server that accepts a serialized instance of a LogEntry object. So when a smart client has an exception it will create an instance of the LogEntry and call the web service. The web service then gets the log message into a centralized database. From one location we can view all log messages from all the applications. And, of course, if something happens and the system can't send the log to the web service the logging system will push it into the local Application Event log on the client box so that at least it is captured.
This method keeps us from having to give the end users instructions on locating a file for emailing to us, etc. It also can provide a "live" feed of what's going on and allow for preventative monitoring rather than just reactive (well, it "could" allow for that if there were enough resources and focus on that). Mike 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® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
