If you look at the event handler for the UnhandledException of the
Application object in your App.xaml.cs file, you'll see why. By default,
unhandled exceptions are handled differently when a debugger is attached.
private void Application_UnhandledException(object sender,
Hi Greg,
Presuming it's a Silverlight app, the first thing you can do is attach the
debugger from your dev machine.
That's what's great about Silverlight - it's a client side technology. So when
you hit the website in prod, you're still running the app locally.
Just use VS to 'Attach to
You'd have to begin by assuming some kind of server interaction is causing the
problem - start with fiddler perhaps...
Cheers,
Jordan.
On 21/04/2012, at 5:51 PM, Greg Keogh g...@mira.net wrote:
Folks, I have one of those stinkers where my SL4 app woks nicely on my dev
machine, but when
