<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:pingback="http://madskills.com/public/xml/rss/module/pingback/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>Eran Nachum's Blog</title>
    <link>http://www.eranachum.com/</link>
    <description>www.eranachum.com - Implementing &amp; executing my thoughts...</description>
    <language>en-us</language>
    <copyright>Eran Nachum</copyright>
    <lastBuildDate>Mon, 04 Apr 2011 18:16:00 GMT</lastBuildDate>
    <generator>newtelligence dasBlog 1.8.5223.2</generator>
    <managingEditor>eranachum@hotmail.com</managingEditor>
    <webMaster>eranachum@hotmail.com</webMaster>
    <item>
      <trackback:ping>http://www.eranachum.com/Trackback.aspx?guid=0f38369a-6803-4a31-9166-b71c9ccbc238</trackback:ping>
      <pingback:server>http://www.eranachum.com/pingback.aspx</pingback:server>
      <pingback:target>http://www.eranachum.com/PermaLink,guid,0f38369a-6803-4a31-9166-b71c9ccbc238.aspx</pingback:target>
      <dc:creator>eranachum@hotmail.com (Eran Nachum)</dc:creator>
      <body xmlns="http://www.w3.org/1999/xhtml">
        <p>
      Hi,
   </p>
        <p>
      I read a great post in the ADO.NET team blog in regards using the new EF 4 as a Unit
      of Work design pattern.
   </p>
        <p>
      The main idea under this solution is to maintain all data manipulations against the
      DataBase easily and transactional, by encapsulating all data manipulation on POCO
      objects under a single DataContext and a single Save method.
   </p>
        <p>
      This mechanism is usually recommended when working with asp.net MVC patterns, which
      each of the views is working with its specific controller that communicates with its
      model that implemented as a Repository pattern that exposes an interface of all methods
      signatures.
   </p>
        <p>
      You can impress the post <a href="http://blogs.msdn.com/b/adonet/archive/2009/06/16/using-repository-and-unit-of-work-patterns-with-entity-framework-4-0.aspx" target="_blank">here</a>.
   </p>
        <img width="0" height="0" src="http://www.eranachum.com/aggbug.ashx?id=0f38369a-6803-4a31-9166-b71c9ccbc238" />
      </body>
      <title>Using Repository and Unit of Work patterns with Entity Framework 4.0</title>
      <guid>http://www.eranachum.com/PermaLink,guid,0f38369a-6803-4a31-9166-b71c9ccbc238.aspx</guid>
      <link>http://www.eranachum.com/PermaLink,guid,0f38369a-6803-4a31-9166-b71c9ccbc238.aspx</link>
      <pubDate>Mon, 04 Apr 2011 18:16:00 GMT</pubDate>
      <description>&lt;p&gt;
   Hi,
&lt;/p&gt;
&lt;p&gt;
   I read a great post in the ADO.NET team blog in regards using the new EF 4 as a Unit
   of Work design pattern.
&lt;/p&gt;
&lt;p&gt;
   The main idea under this solution is to maintain all data manipulations against the
   DataBase easily and transactional, by encapsulating all data manipulation on POCO
   objects under a single DataContext and a single Save method.
&lt;/p&gt;
&lt;p&gt;
   This mechanism is usually recommended when working with asp.net MVC patterns, which
   each of the views is working with its specific controller that communicates with its
   model that implemented as a Repository pattern that exposes an interface of all methods
   signatures.
&lt;/p&gt;
&lt;p&gt;
   You can impress the post &lt;a href="http://blogs.msdn.com/b/adonet/archive/2009/06/16/using-repository-and-unit-of-work-patterns-with-entity-framework-4-0.aspx" target="_blank"&gt;here&lt;/a&gt;.
&lt;/p&gt;
&lt;img width="0" height="0" src="http://www.eranachum.com/aggbug.ashx?id=0f38369a-6803-4a31-9166-b71c9ccbc238" /&gt;</description>
      <category>.NET 4;Entity Framework 4;Design Patterns</category>
    </item>
  </channel>
</rss>