rickgaribay.net

Space shuttles aren't built for rocket scientists, they're built for astronauts. The goal isn't the ship, its the moon.
posts - 303, comments - 180, trackbacks - 35

My Links

News

Where's Rick?


AgileAlliance deliver:Agile 2019- 4/29
Desert Code Camp, PHX - 10/11
VS Live Austin, TX - 6/3
VS Live SF - 6/17


About Me
Hands on leader, developer, architect specializing in the design and delivery of distributed systems in lean, agile environments with an emphasis in continuous improvement across people, process and technology. Speaker and published author with 18 years' experience leading the delivery of large and/or complex, high-impact distributed solutions in Retail, Intelligent Transportation, and Gaming & Hospitality.

I'm currently a Principal Engineer at Amazon, within the North America Consumer organization leading our global listings strategy that enable bulk and non-bulk listing experiences for our WW Selling Partners via apps, devices and APIs.

Full bio

Note: All postings on this site are my own and don’t necessarily represent the views of my employer.



Check out my publications on Amazon Kindle!





Archives

Post Categories

Published Works

System.Diagnostics.DebuggerStepThroughAttribute()

It was at the eleventh hour and I am trying to debug a WCF proxy with no luck. I knew that the call was crossing the process boundary because I was catching a Fault Exception, but when its late and things get hinky, I wanted to ensure that I was calling the right method on the channel.

My friend and collegue David Barrett pointed me to the fact that the proxy class is decorated with the following attribute:[System.Diagnostics.DebuggerStepThroughAttribute()]

I am not sure what value this provides, unless you want to hide the details of the proxy from developers when stuck in the muck, but removing the attribute seems to work!

Print | posted on Tuesday, September 25, 2007 9:55 AM | Filed Under [ WCF ]

Comments have been closed on this topic.

Powered by: