<?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>LINQ to SQL Tips 2: how to use common base class for all entities</title><link>http://blogs.msdn.com/dinesh.kulkarni/archive/2007/11/09/linq-to-sql-how-to-2-base-class-for-all-entities.aspx</link><description>Here is another question I get quite often: I have some common fields (maybe id and timestamp) and some common behavior across all my entities. How do I handle that in LINQ to SQL? After all, the only inheritance mapping supported is Table Per Hierarchy</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: LINQ to SQL Tips 2: how to use common base class for all entities</title><link>http://blogs.msdn.com/dinesh.kulkarni/archive/2007/11/09/linq-to-sql-how-to-2-base-class-for-all-entities.aspx#6381380</link><pubDate>Mon, 19 Nov 2007 02:29:46 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6381380</guid><dc:creator>Alexey Lavnikov</dc:creator><description>&lt;p&gt;What was a problem to gather ColumnAttributes &amp;nbsp;from flattened list of properties?&lt;/p&gt;
&lt;p&gt;Doesn't look very pretty to have virtual properties just for mapping purpose...&lt;/p&gt;</description></item><item><title>re: LINQ to SQL Tips 2: how to use common base class for all entities</title><link>http://blogs.msdn.com/dinesh.kulkarni/archive/2007/11/09/linq-to-sql-how-to-2-base-class-for-all-entities.aspx#6427587</link><pubDate>Tue, 20 Nov 2007 12:56:43 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6427587</guid><dc:creator>Martin Laufer</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;You stated, that the sqlmetal tool will accept only one base class for all entities. Will it accept an interface?&lt;/p&gt;
&lt;p&gt;- Martin&lt;/p&gt;
</description></item><item><title>Dinesh Kulkarni's LINQ to SQL tips</title><link>http://blogs.msdn.com/dinesh.kulkarni/archive/2007/11/09/linq-to-sql-how-to-2-base-class-for-all-entities.aspx#8519554</link><pubDate>Mon, 19 May 2008 22:35:24 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8519554</guid><dc:creator>Hot Topics</dc:creator><description>&lt;p&gt;Dinesh Kularni , who was formerly on the LINQ to SQL team and is now on the Silverlight team, has been&lt;/p&gt;
</description></item><item><title>Dinesh Kularni : LINQ To SQL tips</title><link>http://blogs.msdn.com/dinesh.kulkarni/archive/2007/11/09/linq-to-sql-how-to-2-base-class-for-all-entities.aspx#8522113</link><pubDate>Tue, 20 May 2008 11:24:51 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8522113</guid><dc:creator>Matthieu MEZIL</dc:creator><description>&lt;p&gt;Dinesh Kularni a publi&amp;#233; depuis novembre 5&amp;#160;astuces sur LINQ To SQL : LINQ to SQL Tips 1: how to map an&lt;/p&gt;
</description></item><item><title>LINQ to SQL Tips</title><link>http://blogs.msdn.com/dinesh.kulkarni/archive/2007/11/09/linq-to-sql-how-to-2-base-class-for-all-entities.aspx#8701763</link><pubDate>Mon, 07 Jul 2008 16:05:19 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8701763</guid><dc:creator>LaptopHeaven: blogging that bytes</dc:creator><description>&lt;p&gt;I found a series of LINQ to SQL tips over at Dinesh's Cyberstation . LINQ to SQL Tips 1: how to map an enum LINQ to SQL Tips 2: how to use common base class for all entities LINQ to SQL Tips 3: Deferred (lazy) or eager loading of related objects with&lt;/p&gt;
</description></item><item><title>Linq to Sql lifetime</title><link>http://blogs.msdn.com/dinesh.kulkarni/archive/2007/11/09/linq-to-sql-how-to-2-base-class-for-all-entities.aspx#9482042</link><pubDate>Tue, 17 Mar 2009 01:00:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9482042</guid><dc:creator>Iga lahendus tekitab uusi probleeme ehk alati võib leida veel ühe bugi.</dc:creator><description>&lt;p&gt;&amp;#220;ks teemaisd, mis mind m&amp;#245;nda aega on Linq to SQL juures m&amp;#245;tisklema pannud, on selle lifetime ehk kui&lt;/p&gt;
</description></item></channel></rss>