Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>1a: The <a href="http://msdn.microsoft.com/en-us/library/system.diagnostics.debuggerstepthroughattribute.aspx" rel="nofollow">DebuggerStepThough</a> attribute indicates that when a breakpoint is hit and the coder is stepping through the code, the debugger will skip over this method rather than pausing on each line.</p> <p>1b: The <a href="http://msdn.microsoft.com/en-us/library/system.componentmodel.designercategoryattribute.aspx" rel="nofollow">DesignerCategory</a> attribute indicates the grouping for the class if/when it appears in design time controls such as the property grid in visual studio.</p> <p>1c: The <a href="http://msdn.microsoft.com/en-us/library/system.web.services.webservicebindingattribute.aspx" rel="nofollow">WebServiceBinding</a> attribute attaches the name and the namespace to a class which represents a web service.</p> <p>It's important to understand that attributes don't "do" anything, they just contain meta-data and it's up to other parts of code what to do with that meta-data.</p> <p>2: The return statement before the attribute indicates that the attribute applies to the value being returned from the method, not to the method itself. Similarly you can apply attributes to the method parameters. In this case the attribute is describing how the return value should be serialized into XML.</p> <p>3: This is similar to a regular request/response web service call, but it has been modified to be asynchronous. The AsyncCallback is a method that should be called when the asynchronous operation has compelted, and the return value is an AsyncResult which can be used to inspect the running operation from other parts of code. This is the old pattern of asynchronous method calls and you don't find this kind of code much anymore. <a href="http://msdn.microsoft.com/en-us/library/aa719595%28v=vs.71%29.aspx" rel="nofollow">See Async Pattern on MSDN...</a></p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload