<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://weblogs.asp.net/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>Bigyan Rajbhandari - All Comments</title><link>http://weblogs.asp.net/bigyanr/default.aspx</link><description>All about technology...</description><dc:language>en</dc:language><generator>CommunityServer 2007 SP1 (Debug Build: 20510.895)</generator><item><title>re: Best practice and effective way of using DataContext in Linq to SQL?</title><link>http://weblogs.asp.net/bigyanr/archive/2008/03/18/best-practice-and-effective-way-of-using-datacontext-in-linq-to-sql.aspx#7046197</link><pubDate>Tue, 14 Apr 2009 16:51:21 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:7046197</guid><dc:creator>rickoshay</dc:creator><description>&lt;p&gt;Simply inject the context and let the container figure out which one is in effect given the current call chain, nested transaction level and so on. &lt;/p&gt;
&lt;p&gt;[DataContext] Foo() ...&lt;/p&gt;
&lt;p&gt;Oh, wait, they are ten years from an IoC container if MVC is any guide. &lt;/p&gt;
&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=7046197" width="1" height="1"&gt;</description></item></channel></rss>