<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://www.imason.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Organize your Feature Receivers</title><link>http://www.imason.com/imason_Blogs/b/ivan_neganov/archive/2009/01/31/organize-your-feature-receivers.aspx</link><description>Assuming that you deal a lot with installation of various SharePoint components and solutions, and have written custom feature receivers a number of times, you have probably seen the below code fragment each time you wrote a site collection-scoped feature</description><dc:language>en</dc:language><generator>Telligent Evolution 5.0 (Build: 40623.6204)</generator><item><title>re: Organize your Feature Receivers</title><link>http://www.imason.com/imason_Blogs/b/ivan_neganov/archive/2009/01/31/organize-your-feature-receivers.aspx#2245</link><pubDate>Tue, 15 Jun 2010 16:37:16 GMT</pubDate><guid isPermaLink="false">ba1d72eb-a51c-4157-8cec-718d26de3334:2245</guid><dc:creator>Ryan</dc:creator><description>&lt;p&gt;You may also need to deal with Farm and Web Application scoped features when casting properties.Feature.Parent&lt;/p&gt;
&lt;p&gt;I&amp;#39;ve put together a blog post with some of the more esoteric details of how SharePoints Feature Receiver Events work. Thinks like what triggers each event and which account it will run under - not quite as obvious as it first sounds.&lt;/p&gt;
&lt;p&gt;&lt;a rel="nofollow" target="_new" href="http://blog.pentalogic.net/2010/06/sharepoint-feature-receivers-events-details/"&gt;blog.pentalogic.net/.../sharepoint-feature-receivers-events-details&lt;/a&gt;&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://www.imason.com/aggbug.aspx?PostID=2245" width="1" height="1"&gt;</description></item></channel></rss>