A way to handle all the errors...efficiently!
You may say that in the BizTalk Server 2006 version there's a way to subscribe all the suspended messages.
But that's the point. I don't want to subscribe to suspended messages. I want to be alerted when they become suspended. Ok...maybe some of the times subscribing to the suspended messages is all that we need. But to be honest, most of the times I simply want to be notified and then go to the administration console and try to fix the problem.
For you all BTS 2004 users, you're familiar with the listening for a suspended event using WMI. I can still use it in BTS 2006. But that's not the solution. The MSBTS_ServiceInstanceSuspendedEvent isn't very specific about the why, how, what and when variables surrounding the message that is suspended (check out here the properties of this event).
Another reason why listening to this event isn't the solution, is because I can't filter the events that I want to be notified. Mental note to the BizTalk development team: make the concept of "application" an intrinsic part of the BizTalk engine and not just a way to group artifacts in administration console. I would much appreciate to filter based on the application name.
One final reason (that I can think of) is that I don't want to develop anything to run outside the BTS. It's not a good practice!
Feel free to comment on this, and if you think I'm wrong explain me why. I'm eager to learn :)