<?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 a LINQ to SQL or EF Query</title>
	<atom:link href="http://www.ytechie.com/2009/04/unit-testing-a-linq-to-sql-or-ef-query.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.ytechie.com/2009/04/unit-testing-a-linq-to-sql-or-ef-query.html</link>
	<description>Productive software development using ASP.NET, C#, Adobe Flex, and other technologies and tools.</description>
	<lastBuildDate>Fri, 03 Feb 2012 08:52:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Jones</title>
		<link>http://www.ytechie.com/2009/04/unit-testing-a-linq-to-sql-or-ef-query.html/comment-page-1#comment-1422</link>
		<dc:creator>Jones</dc:creator>
		<pubDate>Mon, 27 Apr 2009 21:51:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.ytechie.com/2009/04/unit-testing-a-linq-to-sql-or-ef-query.html#comment-1422</guid>
		<description>Nice post...</description>
		<content:encoded><![CDATA[<p>Nice post&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: superjason</title>
		<link>http://www.ytechie.com/2009/04/unit-testing-a-linq-to-sql-or-ef-query.html/comment-page-1#comment-1411</link>
		<dc:creator>superjason</dc:creator>
		<pubDate>Tue, 14 Apr 2009 12:43:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.ytechie.com/2009/04/unit-testing-a-linq-to-sql-or-ef-query.html#comment-1411</guid>
		<description>The problem is, I want the database call to be efficient. That&#039;s why the logic within the repository call is difficult to avoid. I certainly good return all the data from the table, and move the logic out, but I don&#039;t like that strategy.

Could you explain further what you have in mind?</description>
		<content:encoded><![CDATA[<p>The problem is, I want the database call to be efficient. That&#8217;s why the logic within the repository call is difficult to avoid. I certainly good return all the data from the table, and move the logic out, but I don&#8217;t like that strategy.</p>
<p>Could you explain further what you have in mind?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Typemock</title>
		<link>http://www.ytechie.com/2009/04/unit-testing-a-linq-to-sql-or-ef-query.html/comment-page-1#comment-1409</link>
		<dc:creator>Typemock</dc:creator>
		<pubDate>Tue, 14 Apr 2009 09:25:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.ytechie.com/2009/04/unit-testing-a-linq-to-sql-or-ef-query.html#comment-1409</guid>
		<description>You are correct –it doesn&#039;t scale. You can make it a bit easier on yourself, using a mocking framework (like Typemock Isolator or Rhino)for isolating the database calls, and concentrate on unit-testing the logic itself.</description>
		<content:encoded><![CDATA[<p>You are correct –it doesn&#8217;t scale. You can make it a bit easier on yourself, using a mocking framework (like Typemock Isolator or Rhino)for isolating the database calls, and concentrate on unit-testing the logic itself.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

