No, I know that if you read the Microsoft curriculum, it will tell you how wonderful things like Debug.Assert() are; to a great extent, they are.

The problem with using them in an assembly that is called by BizTalk is that BizTalk runs in an Isolated Host.

What this means is, if you try to do any sort of debuggin in BizTalk with a deployed assembly, you will never see the pretty litle pop-up box.  The worker thread will simply hang in an active state until you kill all of the services and start all over.

They key thing to remeber is that the .Assert method in general pop up a little error message so that we can click OK and carry along on our merry little way.  In BizTalk however, the Isolated Host simply waits for someone to click OK.  The never will, because they can not see the box.

In short, DON'T use Debug.Assert() in an assembly that will be called by BizTalk.

(Oh boy, took me a while to figure out why my BizTalk box was being so lazy)