Shawn S.'s List: Development Knowledge Base

• Generally, a feature represents an amount of work that will span iterations (these are sometimes referred to as epics), PBIs are units of customer value that can be completed in a single iteration, and tasks are units of work that can be completed in a couple of days. Using them this way lets you scope your project view to whatever level of granularity makes sense at the time, whether at the portfolio level or down to the details. There’s a lot more to work items than what I discuss here, and I encourage you to check out the relevant articles on MSDN for more information.

• configure an additional module called Elmah.ErrorFilterModule. Make sure you add it after any of the logging modules from ELMAH
• <add name="ErrorFilter" type="Elmah.ErrorFilterModule, Elmah"/>
• ErrorFilterModule takes care of subscribing to the Filtering event of the modules that precede it.
• If the assertions test true, the exception is dismissed.
• <section name="errorFilter" type="Elmah.ErrorFilterSectionHandler, Elmah"/>
• add the actual section under the <elmah> group
• If the condition is met, the assertion outcome is true.
• The <equal> assertion above has a binding attribute that is actually a data-binding expression that you already know. It is the very same expression and syntax you specify to the Eval method when data-binding within the server-side markup of ASP.NET pages and user controls.
• you have to specify the type of the value expected from the binding expression as well as that of the text in the value attribute
• the current set of comparison assertions are limited to primitive types represented by the TypeCode members (except Empty, DBNull and Object)
• If you omit the type attribute then the value type of String is assumed.
• The <and> is a composite assertion that results to true when all its sub-assertions also result to true. Likewise, you also have the logical <or> and <not> composite assertions.
• you can also use the <jscript> assertion to specify a filtering condition as a simple JavaScript expression
• For versions earlier than ELMAH 1.2 SP2, replace $ in the example above with the undocumented $context
• Filtering By Source

  • This is the source of the filter object (e.g. Log or Mail), not the source of the log entry.
• ELMAH allows filtering based on the source module
• available for binding that enable this are called FilterSource, FilterSourceType and FilterSourceAssemblyName
• The following example shows how to prevent having 404 HTTP errors being mailed.
• public bool Test(object context)

  • Comment below says this method should return an IAssertion
• The factory method must be named after the XML configuration element.
• An underscore may be used in the method name where a dash is expected in the XML element name such that not-equal becomes not_equal
• you need to scope your element to an XML-based namespace whose value provides the necessary hints for the namespace and assembly where the factory class is located.
• f the XML namesapce starts with http://schemas.microsoft.com/clr/nsassem/ then the remaining two path components are extracted as the type namespace followed by the assembly name where the assertion class factory can be found.
• AssertionFactory is simply dot-appended to the type namespace extracted from the XML namespace
• and given the entire XML configuration element as its sole parameter so that it can extract further information needed for the configuration of the actual assertion
• the always_true method is invoked

• For example I wanted to filter Exceptions with a certain Message so my assertion looks like:

     <equal binding="Exception.Message" value="The image is not found." type="String"/>

• the basic expressions available for the binding value, at least the public properties of AssertionHelperContext? that are of interest:

  • Exception
  • BaseException?
  • HttpStatusCode?
  • Context

  where Context is HttpContext? and thus all the usual Request/Response properties are available for inspection.

26 more annotations...

• The X-Frame-Options HTTP response header can be used to indicate whether or not a browser should be allowed to render a page in a <frame> or <iframe>. Sites can use this to avoid clickjacking attacks, by ensuring that their content is not embedded into other sites.

• public void Page_Load(object sender, EventArgs e)

  {

      RegisterAsyncTask(new PageAsyncTask(LoadSomeData));

  }
• await Task.WhenAll(clientcontacts, clienttemperature, clientlocation);
• Newtonsoft.Json.JsonConvert.DeserializeObject<List<Contact>>(await clientcontacts);
• <%@ Page Title="Async"

2 more annotations...

• The case number should be of the form:

    

  \b((FogBug[sz]|Case|Bug[zs]*(?:ID)*):(\d+)

• The Cross-Origin Resource Sharing standard works by adding new HTTP headers that allow servers to describe the set of origins that are permitted to read that information using a web browser.

• window.postMessage is a method for safely enabling cross-origin communication. Normally, scripts on different pages are only allowed to access each other if and only if the pages which executed them are at locations with the same protocol (usually both http), port number (80 being the default for http), and host (modulo document.domain being set by both pages to the same value). window.postMessage provides a controlled mechanism to circumvent this restriction in a way which is secure when properly used.
• otherWindow.postMessage(message, targetOrigin);

• • In the solution explorer, right click the page and select "View component designer" from the context menu
   
  • open the properties panel/window (press F4)
   
  • now click the yellow arrow/flash icon and you will see a list of all page events
   
  • double-click the event for which you want to add a handler

• SubmitChanges();
• [TABLE].InsertOnSubmit([table]);