Help w/ design patterns

Hi,

I've developed a series of  middleware tools to assist in the communication of two management system.  The steps are always the same but depending on the kind of communication there is a little preprocessing of the message.  So I set up a event driven class, so whoever uses the class just has to add an event handler and is good to go.  The events has a signature like this.

Message PreprocessMessage(Message incoming);

But when I pass the libraries thru FxCop, it complained that .Net events should go like this:

void EventHandler(object sender, EventArgs args);

so if I'm not suppossed to use events in such way what is the proper design pattern for it?


Also FxCop complains that I'm catching generic exceptions (yes my bad, I catch the Exception class).  But this is not the regular user friendly programs this ones work as Windows services and the message passing task is critical, so the rationale behind this is: in case of any error, catch it, log it and move on 'cause we can't afford to stop everything just out of one error.  I don't think I have to catch every single kind of exception just to please FxCop, or what is the rigth pattern for this, given that it is supposed to work 24x7.