<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://aspadvice.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>Visual Studio 2005 Team System - Blessing or Anathema?</title><link>http://aspadvice.com/forums/365/ShowForum.aspx</link><description>Visual Studio 2005 Team System clearly plays a role in increasing the productivity and predictability of software development through the careful integration of tools and process. There are many positive aspects the product suite professes that may very likely herald a new era of efficiency for software architects and developers. Is all what Team System promises a good thing? Are there drawbacks to this approach? Join us to discuss what you feel are the best and worst things about the Team System vision.</description><dc:language>en</dc:language><generator>CommunityServer 2.1 (Build: 60809.935)</generator></channel></rss>