This seems to be something that would be fairly commonly needed, but I haven't been able to find out how to do it. So apologies if this is covered in the documentation somewhere.
I need to catch the errors that show up and show some custom error text that is more user-friendly. For a timeout, I want to show something like "Report generation timed out, please try again.". What I don't want to show an end user is a full stack trace that shows up by default. So how can I capture the error, and change what gets displayed?
I have actually seen two different time out messages. The most common one (attached: silverlighttelerikerrordisplay.png), and one I've only seen once (second attachment: silverlightteleriktimeout2.png). If I could get it to do this simpler, second option all the time, I could live with that.
Also, I've tried dealing with the error message in the RenderAndCacheComplete event handler. However, the best I can do is put another control on the screen that has some text in it, which ends up looking like the third attachment (customerrorbox.png). If I could find a way to clear the content of the built-in error page, I could probably live with this option too.
Any other ideas, or ways to improve the two potential options above?
TIA,
-David
I need to catch the errors that show up and show some custom error text that is more user-friendly. For a timeout, I want to show something like "Report generation timed out, please try again.". What I don't want to show an end user is a full stack trace that shows up by default. So how can I capture the error, and change what gets displayed?
I have actually seen two different time out messages. The most common one (attached: silverlighttelerikerrordisplay.png), and one I've only seen once (second attachment: silverlightteleriktimeout2.png). If I could get it to do this simpler, second option all the time, I could live with that.
Also, I've tried dealing with the error message in the RenderAndCacheComplete event handler. However, the best I can do is put another control on the screen that has some text in it, which ends up looking like the third attachment (customerrorbox.png). If I could find a way to clear the content of the built-in error page, I could probably live with this option too.
Any other ideas, or ways to improve the two potential options above?
TIA,
-David