<?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: LINQ to SQL tips and tricks #2</title>
	<atom:link href="http://damieng.com/blog/2009/04/12/linq-to-sql-tips-and-tricks-2/feed" rel="self" type="application/rss+xml" />
	<link>http://damieng.com/blog/2009/04/12/linq-to-sql-tips-and-tricks-2</link>
	<description>A .NET developer in Redmond</description>
	<lastBuildDate>Sun, 14 Mar 2010 14:22:22 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Maxim&#8217;s blog &#187; links for 2009-04-16</title>
		<link>http://damieng.com/blog/2009/04/12/linq-to-sql-tips-and-tricks-2#comment-14946</link>
		<dc:creator>Maxim&#8217;s blog &#187; links for 2009-04-16</dc:creator>
		<pubDate>Thu, 16 Apr 2009 18:18:48 +0000</pubDate>
		<guid isPermaLink="false">http://damieng.com/blog/2009/04/12/linq-to-sql-tips-and-tricks-2#comment-14946</guid>
		<description>[...] LINQ to SQL tips and tricks #2 [...]</description>
		<content:encoded><![CDATA[<p>[...] LINQ to SQL tips and tricks #2 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Damien Guard</title>
		<link>http://damieng.com/blog/2009/04/12/linq-to-sql-tips-and-tricks-2#comment-14655</link>
		<dc:creator>Damien Guard</dc:creator>
		<pubDate>Mon, 13 Apr 2009 23:00:56 +0000</pubDate>
		<guid isPermaLink="false">http://damieng.com/blog/2009/04/12/linq-to-sql-tips-and-tricks-2#comment-14655</guid>
		<description>@Brent that guidance was specifically issued because it is not clear from the name whether copies are deep or shallow and that people consuming your framework wouldn&#039;t know which the object has chosen.

In your own internal classes this is not so much of a problem but yes, if you like, you can create your own Clone/Copy methods without using ICloneable instead.

[)amien</description>
		<content:encoded><![CDATA[<p>@Brent that guidance was specifically issued because it is not clear from the name whether copies are deep or shallow and that people consuming your framework wouldn&#8217;t know which the object has chosen.</p>
<p>In your own internal classes this is not so much of a problem but yes, if you like, you can create your own Clone/Copy methods without using ICloneable instead.</p>
<p>[)amien</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brent Miller</title>
		<link>http://damieng.com/blog/2009/04/12/linq-to-sql-tips-and-tricks-2#comment-14652</link>
		<dc:creator>Brent Miller</dc:creator>
		<pubDate>Mon, 13 Apr 2009 22:32:11 +0000</pubDate>
		<guid isPermaLink="false">http://damieng.com/blog/2009/04/12/linq-to-sql-tips-and-tricks-2#comment-14652</guid>
		<description>Brad Abrams (and the .NET team) recommends people don&#039;t implement ICloneable:
http://blogs.msdn.com/brada/archive/2003/04/09/49935.aspx</description>
		<content:encoded><![CDATA[<p>Brad Abrams (and the .NET team) recommends people don&#8217;t implement ICloneable:<br />
<a href="http://blogs.msdn.com/brada/archive/2003/04/09/49935.aspx" rel="nofollow">http://blogs.msdn.com/brada/archive/2003/04/09/49935.aspx</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dew Drop - April 13, 2009 &#124; Alvin Ashcraft's Morning Dew</title>
		<link>http://damieng.com/blog/2009/04/12/linq-to-sql-tips-and-tricks-2#comment-14605</link>
		<dc:creator>Dew Drop - April 13, 2009 &#124; Alvin Ashcraft's Morning Dew</dc:creator>
		<pubDate>Mon, 13 Apr 2009 12:05:55 +0000</pubDate>
		<guid isPermaLink="false">http://damieng.com/blog/2009/04/12/linq-to-sql-tips-and-tricks-2#comment-14605</guid>
		<description>[...] LINQ to SQL tips and tricks #2 (Damien Guard) [...]</description>
		<content:encoded><![CDATA[<p>[...] LINQ to SQL tips and tricks #2 (Damien Guard) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://damieng.com/blog/2009/04/12/linq-to-sql-tips-and-tricks-2#comment-14599</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Mon, 13 Apr 2009 11:20:31 +0000</pubDate>
		<guid isPermaLink="false">http://damieng.com/blog/2009/04/12/linq-to-sql-tips-and-tricks-2#comment-14599</guid>
		<description>I honestly read the first line as &quot;when LINQ to SQL doesn&#039;t want to cock up the TSQL&quot; and thought wow, that&#039;s a divergence from the new professional style :) I guess that says more about me as a reader...</description>
		<content:encoded><![CDATA[<p>I honestly read the first line as &#8220;when LINQ to SQL doesn&#8217;t want to cock up the TSQL&#8221; and thought wow, that&#8217;s a divergence from the new professional style :) I guess that says more about me as a reader&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
