C# Automatic Error Reporting
Contents |
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 .net crash reporting Us Learn more about Stack Overflow the company Business Learn more about hiring
.net Error Reporting
developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join
Windows Error Reporting
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 Error-reporting framework for .net up
Elmah
vote 8 down vote favorite 3 is there an error-reporting-framework you would suggest for use in .net. I need possibilities like e-mail-reporting with fileappending to e-mail. The user should have the possibility to add information to the report and also should have the possibility to remove report-files, i.e. if they contains privacy-critical data. There also should be a possibility of taking an automated screenshot. The needed log4net framework should also include error-reporting guis. It should give me the possibility to create own guis for error-reporting. I already use log4net, but there it isn't possible, as far as i know, to show a gui for error-reporting to the user. Would be nice if there are any advices, Greetings, Martin c# .net error-handling error-reporting bug-tracking share|improve this question edited Feb 9 '10 at 8:47 asked Dec 15 '09 at 8:41 martin 1,74521536 1 See also stackoverflow.com/questions/49224/… –dan-gph Aug 2 '10 at 1:17 Visual Studio Application Insights is what you need! azure.microsoft.com/en-us/documentation/articles/… –smedasn Apr 24 at 15:51 add a comment| 9 Answers 9 active oldest votes up vote 4 down vote Have you tried Elmah? It does all the error handling elements you are talking of. You might look at Trac for the bug-tacking bits you want. Kindness, Dan share|improve this answer answered Dec 15 '09 at 8:43 Daniel Elliott 15.9k94073 add a comment| up vote 4 down vote I am familiar with the "Microsoft Enterprise Library Logging Block" and "Log4Net" and both of these fit into your requirements (having multiple log listeners) Here is a page that compares these two: http://weblogs.asp.net/lorenh/archive/20
Latest Articles Latest Tips/Tricks Top Articles Beginner Articles Technical Blogs Posting/Update Guidelines Article Help Forum Article Competition Submit an article or tip Post your Blog quick answersQ&A Ask a Question about this article Ask a Question View Unanswered Questions View All Questions... C# questions Linux questions ASP.NET questions SQL questions VB.NET questions discussionsforums All Message Boards... Application Lifecycle> Running a Business Sales / Marketing Collaboration / Beta Testing Work Issues Design and Architecture ASP.NET http://stackoverflow.com/questions/1906006/error-reporting-framework-for-net JavaScript C / C++ / MFC> ATL / WTL / STL Managed C++/CLI C# Free Tools Objective-C and Swift Database Hardware & Devices> System Admin Hosting and Servers Java .NET Framework Android iOS Mobile SharePoint Silverlight / WPF Visual Basic Web Development Site Bugs / Suggestions Spam and Abuse Watch features Competitions News The Insider http://www.codeproject.com/Articles/24437/Automatic-Error-Handling Newsletter The Daily Build Newsletter Newsletter archive Surveys Product Showcase Research Library CodeProject Stuff communitylounge Who's Who Most Valuable Professionals The Lounge The Insider News The Weird & The Wonderful The Soapbox Press Releases Non-English Language > General Indian Topics General Chinese Topics help What is 'CodeProject'? General FAQ Ask a Question Bugs and Suggestions Article Help Forum Site Map Advertise with us About our Advertising Employment Opportunities About Us Articles » General Programming » Exception Handling » General ArticleBrowse CodeStatsRevisionsAlternatives Comments (6) Add your ownalternative version Tagged as C#.NET.NET2.0ASP.NETDev Stats 39.7K views990 downloads76 bookmarked Posted 17 Mar 2008 Automatic Error Handling Andy Searls, 17 Mar 2008 CPOL 4.45 (10 votes) 1 2 3 4 5 4.45/5 - 10 votesμ 4.45, σa 1.48 [?] Rate this: Please Sign up or sign in to vote. Handle web and WinForms exceptions automatically. Download source - 52.1 KB Introduction Microsoft’s best practices[1] regarding error handling are pretty clear. They are designed to avoid los
desktop application January 23rd, 2010 – Desktop Development (.NET, C#, How-To, Windows) 3 Comments » If you're writing a .NET desktop application that you intend to distribute then http://stevenbenner.com/2010/01/reporting-of-unhandled-exceptions-in-your-distributable-net-application/ you may find it very helpful to build a system for reporting any exceptions that end-users experience back to you. Being able to gather raw exception reports from https://books.google.com/books?id=bG_Aqb6iOUYC&pg=PA6&lpg=PA6&dq=c%23+automatic+error+reporting&source=bl&ots=PDU5vAfJt4&sig=Zu2DS5VgdTDLjb6BxHmrfkdeDgM&hl=en&sa=X&ved=0ahUKEwjcu_Ory7bPAhUE4oMKHZG9C_sQ6AEIUjAI an app somewhere in the wild will make it much easier to find problems that never appeared on your development and testing environments. This can save you a error reporting lot of headaches when dealing with users complaining about problems that you simply cannot reproduce. An error reporting system has the added benefit of improving end-user morale. It makes people feel much better when they know the developer has received a real report about the problem they encountered. My method for handling exceptions and reporting them is c# automatic error very simple. However, it does require a little extra work to setup. I'll walk you through my particular method and give you the basic C# code that I use. The system There are four pieces to this reporting system: A class to process and log exceptions. Attach functions to the UnhandledException and ThreadException events. Build and distribute a separate Windows Form Application in your solution to report the exceptions back. Create a hosted web application to receive and process the submitted exception reports. The ErrorLog class This is a simple class that I wrote to process an exception passed to it and save the information to a text file. The code is all pretty much self-explanatory so I won't go in to too much detail here. I do want to point out that I am saving the error logs into the ApplicationData folder. This is standard practice since Windows Vista came out because UAC might stop you from saving files anywhere else on the system. public sealed class ErrorLo
thorough reference to the language in one straightforward and accessible volume. Designed as a handbook for daily use, this book is an essential guide to the C# language and the base class APIs of the .NET Framework. Programmers will want to...https://books.google.ca/books/about/C_in_a_Nutshell.html?id=bG_Aqb6iOUYC&utm_source=gb-gplus-shareC# in a NutshellMy libraryHelpAdvanced Book SearchGet print bookNo eBook availableO'ReillyAmazon.caChapters.indigo.caFind in a libraryAll sellers»Get Textbooks on Google PlayRent and save from the world's largest eBookstore. Read, highlight, and take notes, across web, tablet, and phone.Go to Google Play Now »C# in a NutshellPeter Drayton, Ben Albahari, Ted Neward"O'Reilly Media, Inc.", 2003 - Computers - 897 pages 3 Reviewshttps://books.google.ca/books/about/C_in_a_Nutshell.html?id=bG_Aqb6iOUYCC# in a Nutshellprovides C# programmers with a concise and thorough reference to the language in one straightforward and accessible volume. Designed as a handbook for daily use, this book is an essential guide to the C# language and the base class APIs of the .NET Framework. Programmers will want to keep this book next to their keyboards for years to come. The heart of the book is a succinct but detailed reference to the C# language and the .NET types most essential to C# programmers. Each chapter in the API reference begins with an overview of a .NET namespace and a diagram of its types, including a quick-reference entry for each type, with name, assembly, category, description, member availability, class hierarchy, and other relevant information, such as whether the type is part o the ECMA CLI specification. Newly updated for .NET Framework version 1.1, the second edition also adds a CD that allows you to integrate the book's API Quick Reference directly into the help files of Visual Studio .NET 2002 & 2003, giving you direct access to this valuable information via your computer. In addition to the API reference section, this book includes: An accelerated introduction to the C# language and the