<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Installing a Theme as a SharePoint Feature</title>
	<atom:link href="http://www.devexpertise.com/2009/02/11/installing-a-theme-as-a-sharepoint-feature/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.devexpertise.com/2009/02/11/installing-a-theme-as-a-sharepoint-feature/</link>
	<description>Practical tips and tricks for all things .NET, SharePoint, Silverlight, InfoPath, and general application development.</description>
	<lastBuildDate>Wed, 12 May 2010 15:57:34 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jennifer</title>
		<link>http://www.devexpertise.com/2009/02/11/installing-a-theme-as-a-sharepoint-feature/comment-page-1/#comment-1280</link>
		<dc:creator>Jennifer</dc:creator>
		<pubDate>Wed, 12 May 2010 14:23:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.devexpertise.com/2009/02/11/installing-a-theme-as-a-sharepoint-feature/#comment-1280</guid>
		<description>Very cool. Thanks for sharing!</description>
		<content:encoded><![CDATA[<p>Very cool. Thanks for sharing!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DevExpert</title>
		<link>http://www.devexpertise.com/2009/02/11/installing-a-theme-as-a-sharepoint-feature/comment-page-1/#comment-1128</link>
		<dc:creator>DevExpert</dc:creator>
		<pubDate>Sat, 15 Aug 2009 14:48:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.devexpertise.com/2009/02/11/installing-a-theme-as-a-sharepoint-feature/#comment-1128</guid>
		<description>Ron, I definitely understand wanting complete solutions, but there isn&#039;t anything else that is needed other than what&#039;s in this post. All you need is an assembly that has the FeatureReceiver class and a feature.xml file -- that&#039;s it.</description>
		<content:encoded><![CDATA[<p>Ron, I definitely understand wanting complete solutions, but there isn&#8217;t anything else that is needed other than what&#8217;s in this post. All you need is an assembly that has the FeatureReceiver class and a feature.xml file &#8212; that&#8217;s it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ron</title>
		<link>http://www.devexpertise.com/2009/02/11/installing-a-theme-as-a-sharepoint-feature/comment-page-1/#comment-1121</link>
		<dc:creator>Ron</dc:creator>
		<pubDate>Tue, 11 Aug 2009 21:15:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.devexpertise.com/2009/02/11/installing-a-theme-as-a-sharepoint-feature/#comment-1121</guid>
		<description>It would be awesone if you could share the whole sample project source code. This doesn&#039;t give the complete picture of how to create the project/solution. Thanks!</description>
		<content:encoded><![CDATA[<p>It would be awesone if you could share the whole sample project source code. This doesn&#8217;t give the complete picture of how to create the project/solution. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kant</title>
		<link>http://www.devexpertise.com/2009/02/11/installing-a-theme-as-a-sharepoint-feature/comment-page-1/#comment-1104</link>
		<dc:creator>kant</dc:creator>
		<pubDate>Fri, 10 Jul 2009 12:13:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.devexpertise.com/2009/02/11/installing-a-theme-as-a-sharepoint-feature/#comment-1104</guid>
		<description>The only complete material to deploy custom theme as a feature is here !!Good one</description>
		<content:encoded><![CDATA[<p>The only complete material to deploy custom theme as a feature is here !!Good one</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DevExpert</title>
		<link>http://www.devexpertise.com/2009/02/11/installing-a-theme-as-a-sharepoint-feature/comment-page-1/#comment-1028</link>
		<dc:creator>DevExpert</dc:creator>
		<pubDate>Wed, 27 May 2009 15:31:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.devexpertise.com/2009/02/11/installing-a-theme-as-a-sharepoint-feature/#comment-1028</guid>
		<description>Michael,

You are correct (others have pointed this out to me as well)!  Take a look at the updated post to see my corrections.  Thanks for pointing this out!</description>
		<content:encoded><![CDATA[<p>Michael,</p>
<p>You are correct (others have pointed this out to me as well)!  Take a look at the updated post to see my corrections.  Thanks for pointing this out!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DevExpert</title>
		<link>http://www.devexpertise.com/2009/02/11/installing-a-theme-as-a-sharepoint-feature/comment-page-1/#comment-1027</link>
		<dc:creator>DevExpert</dc:creator>
		<pubDate>Wed, 27 May 2009 15:30:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.devexpertise.com/2009/02/11/installing-a-theme-as-a-sharepoint-feature/#comment-1027</guid>
		<description>You are absolutely right, and that was an oversight on my part.  The correct approach is to put the code in the FeatureInstalled/FeatureUninstalling events, as these get fired on each and every web front-end.  I&#039;ve updated the post to reflect this.

Thanks for pointing this out!!</description>
		<content:encoded><![CDATA[<p>You are absolutely right, and that was an oversight on my part.  The correct approach is to put the code in the FeatureInstalled/FeatureUninstalling events, as these get fired on each and every web front-end.  I&#8217;ve updated the post to reflect this.</p>
<p>Thanks for pointing this out!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keith Dahlby</title>
		<link>http://www.devexpertise.com/2009/02/11/installing-a-theme-as-a-sharepoint-feature/comment-page-1/#comment-1026</link>
		<dc:creator>Keith Dahlby</dc:creator>
		<pubDate>Wed, 27 May 2009 14:57:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.devexpertise.com/2009/02/11/installing-a-theme-as-a-sharepoint-feature/#comment-1026</guid>
		<description>It&#039;s worth mentioning that FeatureActivated will only fire on the server from which the feature is activated (which happens on install for Farm-scoped features). If you have multiple WFEs, you can use a timer job to run this code on each every server.

Nice use of LINQ to XML!

Cheers ~
Keith</description>
		<content:encoded><![CDATA[<p>It&#8217;s worth mentioning that FeatureActivated will only fire on the server from which the feature is activated (which happens on install for Farm-scoped features). If you have multiple WFEs, you can use a timer job to run this code on each every server.</p>
<p>Nice use of LINQ to XML!</p>
<p>Cheers ~<br />
Keith</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://www.devexpertise.com/2009/02/11/installing-a-theme-as-a-sharepoint-feature/comment-page-1/#comment-1013</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Sun, 26 Apr 2009 10:39:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.devexpertise.com/2009/02/11/installing-a-theme-as-a-sharepoint-feature/#comment-1013</guid>
		<description>As far as I observed, FeatureReceivers only run on one server in a farm, the one where they are activated from. As you directly manipulate the spthemes.xml, this will only happen on one server and won&#039;t be replicated through the farm. When you try to change the theme from another server, you won&#039;t see the theme in the list.</description>
		<content:encoded><![CDATA[<p>As far as I observed, FeatureReceivers only run on one server in a farm, the one where they are activated from. As you directly manipulate the spthemes.xml, this will only happen on one server and won&#8217;t be replicated through the farm. When you try to change the theme from another server, you won&#8217;t see the theme in the list.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
