Quick Tip: Checking for Success in Web Calls -- Visual Studio Magazine

Tips and Tricks

Quick Tip: Checking for Success in Web Calls

No matter how many HTTP codes there are, you really only need to check one property to determine success or failure.

By Peter Vogel
01/25/2018

The problem with making HTTP calls is that there are so many return codes that count as successful -- anything from 200 to 399 is probably OK, for example.

If you're an ASP.NET developer and working with either HttpResponse or HttpResponseMessage objects, you need only check the object's StatusCode property: If the property is set to HttpResponse.IsSuccessCode, then everything worked out.

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/.

Printable Format

comments powered by Disqus

Featured

VS Code 1.130 Expands Agent Host and Review Tools

Microsoft's latest weekly VS Code release advances shared agent sessions, multi-file change review, chat visibility and terminal navigation
Microsoft Agent Framework Makeover: Claws, Loops and Harnesses

Microsoft's newly released Agent Framework Harness packages the loops, planning, memory, context management and safety controls that developers previously had to assemble around AI models themselves.
Visual Studio 2026 Gives Copilot Built-In Skills -- and Makes Them Prove Their Worth

Microsoft is moving Agent Skills beyond bring-your-own instructions by shipping expert-authored workflows with the IDE, while keeping them off by default until testing shows their benefits justify the additional token use.
Copilot AI Billing Shock Met with Meters, Caps and Token-Saving Tools

GitHub is layering spending limits, expanded credit allowances and increasingly granular usage reporting onto Copilot, while Microsoft is reworking Visual Studio and VS Code to expose -- and reduce -- the cost of agentic development.