BUGBUG: poor title

So, a Silverlight app we recently deployed into production works great across a wide variety of machines, browsers, and even OS platforms…except for one poor customer.  For him the app crashes soon after loading, with a strange exception deep in the SL runtime.  Sounds like a job for the remote debugger, right?

Bzzt.  I think we don't support remote Windows debugging for Silverlight.  Can anyone confirm or deny?

It sure doesn’t work for me.  I can choose a browser from the list of processes and “Silverlight code” from the list of debuggers, but I always get “Unable to attach to the process.”