<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Unit Testing to move into Visual Studio Professional</title>
	<atom:link href="http://blog.coryfoy.com/2007/03/unit-testing-to-move-into-visual-studio-professional/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.coryfoy.com/2007/03/unit-testing-to-move-into-visual-studio-professional/</link>
	<description>It&#039;s all about delivering</description>
	<lastBuildDate>Wed, 08 Feb 2012 16:42:53 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: TravisO</title>
		<link>http://blog.coryfoy.com/2007/03/unit-testing-to-move-into-visual-studio-professional/comment-page-1/#comment-179</link>
		<dc:creator>TravisO</dc:creator>
		<pubDate>Wed, 06 Jun 2007 09:04:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.cornetdesign.com/?p=160#comment-179</guid>
		<description>I understand from a marketing persective why MS wouldn&#039;t want Unit Testing within the framework, but from a developer standpoint it should be.  If it was built into the framework then it would be more accessible for all .Net developers.&lt;br /&gt;&lt;br /&gt;History has shown that exclusion hurts in the long run, and Microsoft can still profit even if VS Express has more advanced features such as Unit Tests, because they still have to sell Windows Server 200x and SQL 200x licenses.  Don&#039;t forget the classic concept that the tighter the grip, the faster that things slip between your fingers, it holds true here.&lt;br /&gt;&lt;br /&gt;Considering that .Net is a developer thing, these kinds of decisions are best left up to the actual developers, not suits or marketeers.</description>
		<content:encoded><![CDATA[<p>I understand from a marketing persective why MS wouldn&#8217;t want Unit Testing within the framework, but from a developer standpoint it should be.  If it was built into the framework then it would be more accessible for all .Net developers.</p>
<p>History has shown that exclusion hurts in the long run, and Microsoft can still profit even if VS Express has more advanced features such as Unit Tests, because they still have to sell Windows Server 200x and SQL 200x licenses.  Don&#8217;t forget the classic concept that the tighter the grip, the faster that things slip between your fingers, it holds true here.</p>
<p>Considering that .Net is a developer thing, these kinds of decisions are best left up to the actual developers, not suits or marketeers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Bock</title>
		<link>http://blog.coryfoy.com/2007/03/unit-testing-to-move-into-visual-studio-professional/comment-page-1/#comment-180</link>
		<dc:creator>Jason Bock</dc:creator>
		<pubDate>Sun, 01 Apr 2007 21:21:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.cornetdesign.com/?p=160#comment-180</guid>
		<description>Brad didn&#039;t suggest putting it into the &quot;language&quot;; just so that it&#039;s available with the standard installation of .NET (just like MSBuild is). And I completely agree with Brad. Having a testing framework that&#039;s not part of the Framework is quite ridiculous, esp. when MSBuild is.</description>
		<content:encoded><![CDATA[<p>Brad didn&#8217;t suggest putting it into the &#8220;language&#8221;; just so that it&#8217;s available with the standard installation of .NET (just like MSBuild is). And I completely agree with Brad. Having a testing framework that&#8217;s not part of the Framework is quite ridiculous, esp. when MSBuild is.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

