<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Threading on Matt Thornton</title>
    <link>https://matt-thornton.net/tags/threading/</link>
    <description>Recent content in Threading on Matt Thornton</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Fri, 02 Mar 2012 18:24:06 +0000</lastBuildDate><atom:link href="https://matt-thornton.net/tags/threading/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>SharePoint Event Receivers &#43; ItemAdded &#43; Null Columns fun</title>
      <link>https://matt-thornton.net/tech/sharepoint/sharepoint-event-receivers-itemadded-null-columns-fun/</link>
      <pubDate>Fri, 02 Mar 2012 18:24:06 +0000</pubDate>
      
      <guid>https://matt-thornton.net/tech/sharepoint/sharepoint-event-receivers-itemadded-null-columns-fun/</guid>
      
        <description>&lt;p&gt;Event receivers enable you to run some action when a particular event occurs. For example, every time a new item is added to a list, you may want to run some code, or start a workflow. This is really handy - but be aware of some gotchas. SharePoint event receivers will generally be one of two types - an “-ing” event or an “-ed” event, such as ItemAdding or ItemAdded. As their name suggests, an -ing event runs &lt;em&gt;whilst&lt;/em&gt; the the event is happening (and might therefore give you the option to cancel it) and -ed events occur &lt;em&gt;after&lt;/em&gt; the event has occurred. You need to be aware of how these events run. Generally, the -ing events run &lt;em&gt;synchronously&lt;/em&gt;, that is, they are blocking and run in the same thread/cycle that they were generated in, and -ed events run &lt;em&gt;asynchronously&lt;/em&gt;, meaning the opposite - they are not blocking - they will be run in a separate thread and not block the execution of the main thread. You therefore need to be aware of what info may, or may not, be available to you when you run code in an event receiver.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>