API: trying to catch '300' errors

[tommam]

I am trying to implement some code to catch the case where the server has invalidated the security ticket and is throwing a "300" error. I implemented some Partial Classes for DocumentService and Item Service, capturing the "Invoke" method and handling the 300 error there. I was able to compile and run the code fine, but when I put a breakpoint in the "Invoke" method and tested, it never hit it.

Then I opened the source code for "ProductstreamItemEditor" and put breakpoints in the same "Invoke" methods, and ran it, but the breakpoints were never hit.

Has anyone gotten this to work? Am I missing something obvious?

Thanks,
Tom

[Anonymous]

The generated web service code disables breakpoints by default.

Here is how you make the breakpoint active:
1. Use the "Show all files" option in your Solution Explorer.
2. Expand out the service you want to debug and find the Reference.cs or
Reference.vb file.
3. Find the declaration of the service class.
4. Comment out the System.Diagnostics.DebuggerStepThroughAttribute
attribute.
5. Recompile and run. The Invoke breakpoint should now be enabled.

--
-- Doug Redmond
Software Engineer, Autodesk Inc.
http://justonesandzeros.typepad.com/

[tommam]

Worked great! Thanks!