<?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>Version Control API changes in TFS 2010 - part I</title><link>http://blogs.msdn.com/michalma/archive/2009/06/15/version-control-api-changes-in-tfs-2010-part-i.aspx</link><description>As Matt writes in his post , the way version control behaves in TFS 2010 has changed in a few significant ways. Our team was responsible for making the client code updates in response to those server changes and I tried to write down lessons we have learned.</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>VSTS Links – 06/17/2009</title><link>http://blogs.msdn.com/michalma/archive/2009/06/15/version-control-api-changes-in-tfs-2010-part-i.aspx#9769801</link><pubDate>Wed, 17 Jun 2009 19:35:16 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9769801</guid><dc:creator>Team System News</dc:creator><description>&lt;p&gt;MichaelMa on Version Control API changes in TFS 2010 – Part 1 The VSTS Quality Tools Blog on 10-4 Episode&lt;/p&gt;
</description></item></channel></rss>