<?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>Brian Harry's explanation of Rosario</title><link>http://blogs.msdn.com/buckh/archive/2006/12/20/brian-harry-s-explanation-of-rosario.aspx</link><description>Brian's post What's in a Code Name? provides some explanation behind the Orcas and Rosario code names. You won't hear the word "Rosario" normally, and here's a bit on why. What's in a Code Name? Mary Jo Foley is writing about one Microsoft code name per</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>VSTS Links - 01/03/2007</title><link>http://blogs.msdn.com/buckh/archive/2006/12/20/brian-harry-s-explanation-of-rosario.aspx#1404884</link><pubDate>Wed, 03 Jan 2007 17:09:46 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1404884</guid><dc:creator>Team System News</dc:creator><description>&lt;p&gt;Martin Hinshelwood on Tim That Task VSTS Check-In Policy. Brian Harry on New TFS Tools Available....&lt;/p&gt;
</description></item></channel></rss>