Practical .NET

Send the Right Error Information with HttpException

When something goes wrong with your Web Service the decent thing to do is to return your errors in a variety of ways.

One way to return an error from a Web Service is to raise an HttpException. If you do so, you should support two methods and one property on the HttpException object:

  • GetHttpCode: One of the HTTP protocol's predefined codes
  • GetHtmlMessage: An HTML-formatted message suitable for display in a Web page
  • Message: A plain text string containing useful information about the error

Probably the easiest way to do this is to pass the exception that your service ran into as the third parameter when creating the HttpException object. The odds are good that the ErrorFormatter that generates the HttpException object's HTML will be able to convert your exception into HTML.

Your resulting code would look like this (using 500, the standard HTTP code for "something has gone horribly wrong on the server"):

Try
  '...code with potential problem...
Catch (ex As Exception)
  Throw New Exception(500, "Something has gone horribly wrong", ex)
End Try

Now, that's a strong message no one can ignore.

About the Author

Peter Vogel is a system architect and principal in PH&V Information Services. PH&V provides full-stack consulting from UX design through object modeling to database design. Peter tweets about his VSM columns with the hashtag #vogelarticles. His blog posts on user experience design can be found at http://blog.learningtree.com/tag/ui/.

comments powered by Disqus

Featured

  • VS Code v1.99 Is All About Copilot Chat AI, Including Agent Mode

    Agent Mode provides an autonomous editing experience where Copilot plans and executes tasks to fulfill requests. It determines relevant files, applies code changes, suggests terminal commands, and iterates to resolve issues, all while keeping users in control to review and confirm actions.

  • Windows Community Toolkit v8.2 Adds Native AOT Support

    Microsoft shipped Windows Community Toolkit v8.2, an incremental update to the open-source collection of helper functions and other resources designed to simplify the development of Windows applications. The main new feature is support for native ahead-of-time (AOT) compilation.

  • New 'Visual Studio Hub' 1-Stop-Shop for GitHub Copilot Resources, More

    Unsurprisingly, GitHub Copilot resources are front-and-center in Microsoft's new Visual Studio Hub, a one-stop-shop for all things concerning your favorite IDE.

  • Mastering Blazor Authentication and Authorization

    At the Visual Studio Live! @ Microsoft HQ developer conference set for August, Rockford Lhotka will explain the ins and outs of authentication across Blazor Server, WebAssembly, and .NET MAUI Hybrid apps, and show how to use identity and claims to customize application behavior through fine-grained authorization.

  • Linear Support Vector Regression from Scratch Using C# with Evolutionary Training

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the linear support vector regression (linear SVR) technique, where the goal is to predict a single numeric value. A linear SVR model uses an unusual error/loss function and cannot be trained using standard simple techniques, and so evolutionary optimization training is used.

Subscribe on YouTube