<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.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>MSDN: &amp;quot;The Highlander&amp;quot; and there will be only one!</title><link>http://blogs.msdn.com/innovation/archive/2008/04/29/msdn-highlander-there-will-be-only-one.aspx</link><description>Building and evolving the MSDN site is a challenge. I am not stating this to try to impress you with a “gee that is hard" vibe, but to acknowledge that when you run systems and sites that have histories that span multi-year life cycles (decades wrt MSDN</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: MSDN: "The Highlander" and there will be only one!</title><link>http://blogs.msdn.com/innovation/archive/2008/04/29/msdn-highlander-there-will-be-only-one.aspx#8573831</link><pubDate>Wed, 04 Jun 2008 22:09:56 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8573831</guid><dc:creator>someone</dc:creator><description>&lt;p&gt;Yeah and what's the catch? Several links are broken! Not even redirects. That's sheer carelessness.&lt;/p&gt;
</description></item></channel></rss>