O'Reilly logo

Inside Microsoft® Exchange Server 2007 Web Services by Huw Upshall, Mark Taylor, Ben Spain, Michael Mainer, David Sterling

Stay ahead with the world's most comprehensive technology and business learning platform.

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, tutorials, and more.

Start Free Trial

No credit card required

Programming Consistency

Programmers using a .NET language are comfortable with errors being reported by exceptions. Component Object Model (COM) and Win32 API programmers from yesteryear are comfortable with HRESULTs and response code values coming back from their calls. As you have seen in this chapter, Exchange Web Services programmers have to contend with a mixture of response values (response codes) and exceptions (SOAP faults). So now that you are here, is there anything that you can do to unify these two error-reporting mechanisms? That all depends on how much of an investment you want to put into extending the auto-generated proxy classes. For instance, if you are writing a simple component that needs to make one call using Exchange Web ...

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, interactive tutorials, and more.

Start Free Trial

No credit card required