http://blogs.msdn.com/aconrad/archive/2009/03/17/updated-linq-to-sql-iupdatable-implementation.aspxBased on feedback from Robert Fonseca-Ensor , I have made a bunch of bug and performance fixes to the IUpdatable implementation for Linq to Sql and posted those to code gallery .&#160; Rob is also now my first official contributor to the project. As parten-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/aconrad/archive/2009/03/17/updated-linq-to-sql-iupdatable-implementation.aspx#9485238Wed, 18 Mar 2009 03:02:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:9485238infoblog &raquo; updated Linq to Sql IUpdatable implementation<p>PingBack from <a rel="nofollow" target="_new" href="http://blog.a-foton.ru/index.php/2009/03/18/updated-linq-to-sql-iupdatable-implementation/">http://blog.a-foton.ru/index.php/2009/03/18/updated-linq-to-sql-iupdatable-implementation/</a></p> http://blogs.msdn.com/aconrad/archive/2009/03/17/updated-linq-to-sql-iupdatable-implementation.aspx#9903655Tue, 06 Oct 2009 13:30:48 GMT91d46819-8472-40ad-a661-2c78acb4018c:9903655Simon<p>Hi,</p> <p>Did you ever write an updated implementation with the 1.5 release? I'm very interested to see if this is improved as I'm considering switching to EM due to issues with the current code.</p> <p>I'm struggling with the clash between relationship fields and their ID fields, e.g.</p> <p>public Customer Customer { ... }</p> <p>public int CustomerID { ... }</p> <p>Both have to be updated to safely update the object.</p> <p>Thanks.</p>