They have the capability within the dev team, but the builds we get do not
contain debuggers - the "cost" in speed and resources is too high and the
benefit too low. Crashes can send data back to Microsoft (if you allow) so
they can analyze and fix the problem but hangs don't generate doc watson
files.

--
Diane Poremsky [MVP - Outlook]
Outlook Tips: http://www.outlook-tips.net/
Outlook & Exchange Solutions Center: http://www.slipstick.com/

Outlook Tips by email:


EMO - a weekly newsletter about Outlook and Exchange:


Poll: What version of Outlook do you use?
http://forums.slipstick.com/showthread.php?t=27072


"Jay Hornsman" wrote in message
...
On Mon, 28 Dec 2009 18:16:44 -0500, "Diane Poremsky [MVP]"
wrote:

if they could detect that it's the outcmd and not the navpane or to-do bar
fail causing the problem, yes. But they often can't detect the cause of
problems.

With all due respect, anyone who believes that has never written a
software application in their lives.

I can believe MS support might not know which one is causing the
problem (although, I believe the command line switches can isolate it
further than the scenario you describe above). But don't spend one
second convincing yourself that the actual developers cannot detect
the cause, with a debugger they can see the exact line of code causing
the issue.