I need to take an existing winforms application and drop into an event tracing mode, with hopefully as little friction as possible.
I would like to see every action the user takes as a simple stack trace-looking thing:
MainForm.LaunchThing_Click ThingWindow.NameInput_Focus ThingWindow.NameInput_TextChanged ThingWindow.AddressInput_Focus ThingWindow.OKButton_Click and so on.
- If this was a WPF application, I would do something like filter all events of type WClientInputMessage in ETW.
- I can’t simply dump a stack trace, because that doesn’t capture the user’s prior actions.
- I could add logging to every single event [with the recommended practices from this discussion], but this is an extant application with far too many events. Plus, I’m lazy. Gotta be a better way.
- I can’t attach a debugger, I want to get this information automatically attached to bug reports from testing users in the field because [it turns out…] nobody can accurately remember exactly what the sequence of things they clicked on was.
So I’m wondering if anyone has any good tricks, using subclassing or reflection perhaps, to latch on to the UI events.
Performance is not really a concern. And if I can get a hook into every event, that’s good enough; I can filter them down to the relevant set fairly easily.
How about an observer pattern? Create an EventLogger class with a bunch of overloaded Log methods (one for each event method signature) that do the logging. Instantiate it on application start and subscribe it to each of the UI events.
It should even be possible to do the subscribing automatically with reflection – though I would think it is more effort to set that up than to do it manually for any reasonably sized application. Also you would still have to ensure that your EventLogger class has a Log method for every possible event handler method signature.