<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Headup - The semantic web - Blog &#187; microsoft silverlight</title>
	<atom:link href="http://blog.headup.com/tag/microsoft-silverlight/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.headup.com</link>
	<description>Semantic Web, Blog widgets, site plugins and everything related to life at Headup.com</description>
	<lastBuildDate>Mon, 07 Mar 2011 09:35:13 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
		<item>
		<title>A detector for memory leaks on Silverlight applications</title>
		<link>http://blog.headup.com/2009/02/a-detector-for-memory-leaks-on-silverlight-applications/</link>
		<comments>http://blog.headup.com/2009/02/a-detector-for-memory-leaks-on-silverlight-applications/#comments</comments>
		<pubDate>Wed, 11 Feb 2009 17:37:45 +0000</pubDate>
		<dc:creator>talk</dc:creator>
				<category><![CDATA[code]]></category>
		<category><![CDATA[for developers]]></category>
		<category><![CDATA[silverlight]]></category>
		<category><![CDATA[developers]]></category>
		<category><![CDATA[memory leak]]></category>
		<category><![CDATA[microsoft silverlight]]></category>

		<guid isPermaLink="false">http://blog.headup.com/?p=266</guid>
		<description><![CDATA[Abstract: Currently there&#8217;s no memory profiler for Silverlight If you’ve ever programmed in Silverlight, you’ve probably wondered whether your objects in memory were collected by the GC (garbage collector) or not. What if the objects you create stay in the memory for the whole life-time of your application – will you know? Regular .NET memory [...]]]></description>
		<wfw:commentRss>http://blog.headup.com/2009/02/a-detector-for-memory-leaks-on-silverlight-applications/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Why Silverlight?</title>
		<link>http://blog.headup.com/2008/12/why-silverlight/</link>
		<comments>http://blog.headup.com/2008/12/why-silverlight/#comments</comments>
		<pubDate>Sun, 21 Dec 2008 09:57:22 +0000</pubDate>
		<dc:creator>talk</dc:creator>
				<category><![CDATA[features]]></category>
		<category><![CDATA[feedback]]></category>
		<category><![CDATA[brian manley]]></category>
		<category><![CDATA[headup]]></category>
		<category><![CDATA[microsoft silverlight]]></category>
		<category><![CDATA[MS silverlight]]></category>
		<category><![CDATA[privacy]]></category>
		<category><![CDATA[silverlight]]></category>

		<guid isPermaLink="false">http://blog.headup.com/?p=95</guid>
		<description><![CDATA[We were rather surprised and even slightly amused by the buzz generated by our choice to base headup on Microsoft&#8217;s Silverlight. The tipping point that lead me to write this post was a tweet from Brian Manley who said: &#8220;Playing with @HeadUp. Pretty cool. Tho the Silverlight requirement is meh&#8220;. A day later Brian twittered: [...]]]></description>
		<wfw:commentRss>http://blog.headup.com/2008/12/why-silverlight/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

