I remembered talking to someone on the Windows Communication Foundation (WCF, previously - Indigo) team before and the reason they chose [MesssageEncoding].MTOM instead of MessageTransmissionOptimizationMechanism is so that it could *at least* fit on a slide.
Well, that someone obviously didnt educate the developer who build the [MessageSecurityVersion]. WSSecurity11WSTrustFebruary2005WSSecureConversationFebruary2005WSSecurityPolicy11BasicSecurityProfile10 property. [Talk about a mouthful]
Not only is it hard to fit on a slide, it would be hard to mouth those words as well.
Besides "bug jail", "secure-programming courses", "geography lessons", I would highly recommend Microsoft engineers and developers go for "Power-Point Presentation Etiquette 101" lessons as well .
Speaking of which, I just got handled an exception with a message like this:
The CLR has been unable to transition from COM context 0x1a0d28 to COM context 0x1a0e98 for 60 seconds. The thread that owns the destination context/apartment is most likely either doing a non pumping wait or processing a very long running operation without pumping Windows messages. This situation generally has a negative performance impact and may even lead to the application becoming non responsive or memory usage accumulating continually over time. To avoid this problem, all single threaded apartment (STA) threads should use pumping wait primitives (such as CoWaitForMultipleHandles) and routinely pump messages during long running operations.
Talk about being explicit. Exceptions should give a friendly message that enables one to have an idea where to start debugging and troubleshooting. The one just made me want to shut my machine down. .