How To Show Error Messages In Asp.net
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up How to display an error message in an ASP.NET Web Application [duplicate] up vote 3 down vote favorite 1 I have an ASP.NET web application, and I wanted to know how I could display an error message box when an exception is thrown. For example, try { do something } catch { messagebox.write("error"); //[This isn't the correct syntax, just what I want to achieve] } [The message box shows the error] Thank you Duplicate of http://stackoverflow.com/questions/651592/how-to-display-an-error-message-box-in-a-web-application-asp-net-c/651601 c# asp.net custom-errors share|improve this question edited May 2 '12 at 16:39 Mr Lister 25k85381 asked Mar 16 '09 at 19:00 zohair 97692137 marked as duplicate by tvanfosson, Andrew Hare, TheTXI, BFree, cgreeno Mar 16 '09 at 19:09 This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question. Duplicate of stackoverflow.com/questions/651592/… –Perchik Mar 16 '09 at 19:03 If you edit the question to link to a duplicate, please put the link at the bottom so it doesn't alter the summary text on the main pages. –Joel Coehoorn Mar 16 '09 at 19:06 @ZOHAIR: You can see your previous questions and their answers at stackoverflow.com/users/70398/zohair –Ramesh Mar 16 '09 at 19:06 ... this is one time when 'Exact Duplicate' isn't going to get any argument. –John MacIntyre Mar 16 '09 at 19:06 That was the point of putting it at the top so people would recognize it as a duplicate and be able to close it more easily. –tvanfosson Mar 16 '09 at 19:07 | show 3 more comments 3 Answers 3 active oldest votes u
resources Windows Server 2012 resources Programs MSDN subscriptions Overview Benefits Administrators Students Microsoft Imagine Microsoft Student Partners ISV Startups TechRewards Events Community Magazine Forums Blogs Channel 9 Documentation APIs and reference Dev centers Samples Retired content We’re sorry. The content you requested has been removed. You’ll be auto redirected in 1 second. MSDN Library MSDN Library MSDN Library MSDN Library Design Tools Development Tools and Languages Mobile and Embedded Development .NET Development Office development Online Services Open Specifications patterns & practices Servers and Enterprise Development Speech Technologies Web Development Windows Desktop App Development TOC Collapse the table of content http://stackoverflow.com/questions/651716/how-to-display-an-error-message-in-an-asp-net-web-application Expand the table of content This documentation is archived and is not being maintained. This documentation is archived and is not being maintained. How to: Display Safe Error Messages Other Versions Visual Studio 2010 .NET Framework 4 Visual Studio 2008 .NET Framework 3.0 Visual Studio 2005 When your application displays error messages, it should not give away information that a malicious user might find helpful https://msdn.microsoft.com/en-us/library/994a1482.aspx in attacking your system. For example, if your application unsuccessfully tries to log in to a database, it should not display an error message that includes the user name it is using. There are a number of ways to control error messages, including the following: Configure the application not to show verbose error messages to remote users. (Remote users are those who request pages while not working on the Web server computer.) You can optionally redirect errors to an application page. Include error handling whenever practical and construct your own error messages. In your error handler, you can test to see whether the user is local and react accordingly. Create a global error handler at the page or application level that catches all unhandled exceptions and routes them to a generic error page. That way, even if you did not anticipate a problem, at least users will not see an exception page. To configure the application to turn off errors for remote users In the Web.config file for your application, make the following changes to the customErrors element: Set the mode attribute to RemoteOnly (case-sensitive). This configures the application to show detailed errors on
ASP.NET web-site, and would like the ability to conditionally show/hide runtime error messages depending on who the user visiting the site is.For a normal user visiting the site you want to be https://weblogs.asp.net/scottgu/Tip_2F00_Trick_3A00_-Show-Detailed-Error-Messages-to-Developers able to display a friendly error message like this when a runtime error occurs: But when someone within the “developers” security role of your application remotely accesses the site you want to instead show a more detailed exception stack trace error message about the problem without having to change any configuration data: The below post describes how to use ASP.NET’s role-based security architecture in conjunction with how to the Global.asax Application_Error event handlerto enable this. You can also download a sample I’ve built that shows how to implement this here.Some Background Discussion on Error Handling and ASP.NET Custom Error Pages:ASP.NET and .NET support a rich error-handling architecture that provides a flexible way to catch/handle errors at multiple levels within an application. Specifically, you can catch and handle a runtime exception with a class, within how to show a page, or on the global application level using the Application_Error event handler within the Global.asax class. If a runtime exception isn’t handled/cancelled by one of these mechanisms, then ASP.NET’s Custom Error Page feature will kick-in, and an error page will be sent back to the browser accessing the application.ASP.NET’s Custom Error Page feature can be used to configure a “friendly error page” to be displayed to end-users in place of the standard “server error occurred” message sent back by ASP.NET. For example, the below web.config file section will cause remote users visiting the site to be redirected to a “friendlyErrorPage.htm” file anytime a runtime error occurs (note: HTTP 500 status code responses indicate runtime errors on the server):