A useful tip that some may not know (apologies if I'm telling anyone how to suck eggs).
Turning on Break on Exceptions in VS (Ctrl-Alt-E then check the Thrown checkbox next to Common Language Runtime Exceptions) can help catch Silverlight/Xaml exceptions. Resharper (5) also seems a lot nicer these days and shows red marks down the right scrollbar where there are Xaml errors. (ie missing event handlers, badly formed xaml etc). It can really help find problems that would normally just crash with no hints as to why. Catastrophic Error anyone? (always brings giggles around the office when i get that one...) cheers, Stephen On Mon, May 10, 2010 at 9:03 PM, Greg Keogh <[email protected]> wrote: > Enable Silverlight debugging in your web app, at least then you can see > which control is causing it (will break in visual studio) > > Nah, it wasn’t getting that far, and debugging was all on. The app xaml > wasn’t loading and I got not useful diagnostic clues anywhere. > > Greg > > _______________________________________________ > ozsilverlight mailing list > [email protected] > http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight > >
_______________________________________________ ozsilverlight mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight
