I use that one alot, but I also use "DebuggerHidden" alot. The difference
(that I observe) is the interaction with Exceptions and "Break on All
exceptions". There are also some breakpoint differences.
In low level code that often gets exceptions (such as calling dispose on a
socket), I would use DebuggerHidden.
--
Chris Mullins, MCSD.NET, MCPD:Enterprise, MVP C#
http://www.coversant.net/blogs/cmullins
"Samuel R. Neff" <sa********@nomail.comwrote in message
news:vr********************************@4ax.com...
>
Decorate the member with
System.Diagnostics.DebuggerStepThroughAttribute.
HTH,
Sam
------------------------------------------------------------
We're hiring! B-Line Medical is seeking Mid/Sr. .NET
Developers for exciting positions in medical product
development in MD/DC. Work with a variety of technologies
in a relaxed team environment. See ads on Dice.com.
On 5 Jan 2007 11:29:18 -0800, "ramadu"
<sr******************@gmail.comwrote:
>>Hi,
I have a utility method in one of my applications which is used
extensively across the application (and it works well). The problem is
that while debugging using Visual Studio, I sometimes forget to skip
debugging for that method (i.e. press F10 instead of F11) and I end up
debugging into that method. Is there any attribute or condition that I
can specify by which I can skip debugging into this utility function?
- Sri