OneTrueError - Automated exception handling

Tag Archives: exceptions

OneTrueError and the WinForms/WPF integration

OneTrueError is a new startup which also is a member of Microsoft BizSpark. This post is about the client library for WinForms/WPF. It will catch and handle all uncaught exceptions automatically. The errors are also uploaded to our site for … Continue reading

Posted in Architecture, CodeProject, OneTrueError | Tagged , , | Leave a comment

OneTrueError and the WCF integration

OneTrueError has a complete WCF integration following the same pattern as WCF. It makes it a breeze to capture and analyze errors in WCF applications.

Posted in Architecture, CodeProject, OneTrueError | Tagged , | Leave a comment

OneTrueError and ASP.NET

OneTrueError is my new startup which also is a member of Microsoft BizSpark. This post is about the client library for ASP.NET (WebForms/MVC/WebAPI). It will catch and handle all uncaught exceptions automatically. The exceptions are also uploaded to our site … Continue reading

Posted in CodeProject, Libraries, OneTrueError | Tagged , | 1 Comment

Updates to OneTrueError

Bug fixes OneTrueError has gotten some bug fixes. A windows update of .NET framework gave us a bit of a down time. Won’t happen again. Fortunately the client library always continue to try to deliver reports if something fails. So … Continue reading

Posted in OneTrueError | Tagged | Leave a comment

Introducing OneTrueError.com

OneTrueError.com is my new startup for .NET developers. It’s a bit like ELMAH, but for most of Microsoft’s different frameworks, and with a tad bit of analytics.

Posted in CodeProject, OneTrueError | Tagged | Leave a comment

Throwing exceptions

Throwing exceptions is in itself trivial. Just invoke throw with an exception object. But when should you throw? Should you create a new exception or rethrow an old one? What should you include in the exception info?

Posted in Architecture, CodeProject | Tagged | 3 Comments

How to design exceptions

This article will teach you how you should design your exception classes. It’s a follow up to my previous article which told you what exceptions are and their intended usage.

Posted in Architecture, CodeProject | Tagged | 1 Comment

What are exceptions?

This blog has been quiet for a while. I am currently writing a book about localization. Me and my partner is also getting close to release of our new startup. One of it’s features is to automatically catch unhandled exceptions … Continue reading

Posted in Architecture, CodeProject | Tagged , | 3 Comments

Dealing with exceptions, Logging and displaying error messages

I got a client which is really firm on that the user should know what went wrong when exceptions are thrown. So we are displaying error messages like “The database did not respond” “The database operation failed” “Failed to load … Continue reading

Posted in Architecture, CodeProject | Tagged | 2 Comments

When to throw exceptions

I’ve written several posts about exceptions. For instance when you should catch them or how you should design them. In this post I’ll discuss when you should throw exceptions. Exceptions are thrown when something exceptional have happended. But what does … Continue reading

Posted in Architecture | Tagged , | 2 Comments