DebuggerStepThroughAttribute Class
Assembly: mscorlib (in mscorlib.dll)
[SerializableAttribute] [AttributeUsageAttribute(AttributeTargets.Class|AttributeTargets.Struct|AttributeTargets.Constructor|AttributeTargets.Method, Inherited=false)] [ComVisibleAttribute(true)] public sealed class DebuggerStepThroughAttribute : Attribute
/** @attribute SerializableAttribute() */ /** @attribute AttributeUsageAttribute(AttributeTargets.Class|AttributeTargets.Struct|AttributeTargets.Constructor|AttributeTargets.Method, Inherited=false) */ /** @attribute ComVisibleAttribute(true) */ public final class DebuggerStepThroughAttribute extends Attribute
The common language runtime attaches no semantics to this attribute. It is provided for use by source code debuggers. For example, the Visual Studio 2005 debugger does not stop in a method marked with this attribute but does allow a breakpoint to be set in the method.
For more information about using attributes, see Extending Metadata Using Attributes.
Windows 98, Windows 2000 SP4, Windows CE, Windows Millennium Edition, Windows Mobile for Pocket PC, Windows Mobile for Smartphone, Windows Server 2003, Windows XP Media Center Edition, Windows XP Professional x64 Edition, Windows XP SP2, Windows XP Starter Edition
The .NET Framework does not support all versions of every platform. For a list of the supported versions, see System Requirements.
This attribute is applied to classes generated by the XSD tool. I ran into trouble debugging a constructor I created for one of these partial classes with this attribute. Unfortunately it took the help of MS to identify why I was getting such odd behavior debugging. The work around is to comment out the attribute in the generated file while you debug.
If it was possible to allow debugging to occur on cetain methods it would be more useful.
- 2/22/2008
- ClimberWill