Comments on: LINQ to SQL tips and tricks #2 http://damieng.com/blog/2009/04/12/linq-to-sql-tips-and-tricks-2?utm_source=rss&utm_medium=rss&utm_campaign=linq-to-sql-tips-and-tricks-2 A .NET developer in silicon valley Fri, 18 May 2012 15:31:00 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Cloning an entity in linq-to-entities « Chandara http://damieng.com/blog/2009/04/12/linq-to-sql-tips-and-tricks-2#comment-45687 Cloning an entity in linq-to-entities « Chandara Sat, 28 May 2011 03:04:42 +0000 http://damieng.com/blog/2009/04/12/linq-to-sql-tips-and-tricks-2#comment-45687 [...] Cloning an entity in linq-to-entities by chandara's blog on May 28, 2011 making a clone of a record and popping it back into the database There are a lot of reason you may want to do something like this, for me, users wanted to be able to make a copy of a huge record so they would then be able to go in and change a few things rather than make a whole new record which was very time consuming. At first, I though of pulling the item, manually copying each property, and inserting… but this is programming, there must be a better way. So then I thought about Reflection and how I might be able to work with that, but that became a big mess that I never got working prior to being discouraged. Next I hit Google, and an awesome blog had a great post to get me on the right track:http://damieng.com/blog/2009/04/12/linq-to-sql-tips-and-tricks-2. [...] [...] Cloning an entity in linq-to-entities by chandara's blog on May 28, 2011 making a clone of a record and popping it back into the database There are a lot of reason you may want to do something like this, for me, users wanted to be able to make a copy of a huge record so they would then be able to go in and change a few things rather than make a whole new record which was very time consuming. At first, I though of pulling the item, manually copying each property, and inserting… but this is programming, there must be a better way. So then I thought about Reflection and how I might be able to work with that, but that became a big mess that I never got working prior to being discouraged. Next I hit Google, and an awesome blog had a great post to get me on the right track:http://damieng.com/blog/2009/04/12/linq-to-sql-tips-and-tricks-2. [...]

]]> By: BGood http://damieng.com/blog/2009/04/12/linq-to-sql-tips-and-tricks-2#comment-41977 BGood Wed, 16 Jun 2010 01:57:00 +0000 http://damieng.com/blog/2009/04/12/linq-to-sql-tips-and-tricks-2#comment-41977 Damian, Thanks for posting your Linq entity cloning code. I hope you don't mind, but (with proper attribution) I translated to VB and referenced it in a thread on MSDN: http://social.msdn.microsoft.com/Forums/en-US/linqtosql/thread/07452e17-9d7c-40ee-beef-d197acd0c59a?prof=required -BGood Damian,

Thanks for posting your Linq entity cloning code. I hope you don’t mind, but (with proper attribution) I translated to VB and referenced it in a thread on MSDN:

http://social.msdn.microsoft.com/Forums/en-US/linqtosql/thread/07452e17-9d7c-40ee-beef-d197acd0c59a?prof=required

-BGood

]]> By: Maxim’s blog » links for 2009-04-16 http://damieng.com/blog/2009/04/12/linq-to-sql-tips-and-tricks-2#comment-14946 Maxim’s blog » links for 2009-04-16 Thu, 16 Apr 2009 18:18:48 +0000 http://damieng.com/blog/2009/04/12/linq-to-sql-tips-and-tricks-2#comment-14946 [...] LINQ to SQL tips and tricks #2 [...] [...] LINQ to SQL tips and tricks #2 [...]

]]> By: Damien Guard http://damieng.com/blog/2009/04/12/linq-to-sql-tips-and-tricks-2#comment-14655 Damien Guard Mon, 13 Apr 2009 23:00:56 +0000 http://damieng.com/blog/2009/04/12/linq-to-sql-tips-and-tricks-2#comment-14655 @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'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 @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’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

]]> By: Brent Miller http://damieng.com/blog/2009/04/12/linq-to-sql-tips-and-tricks-2#comment-14652 Brent Miller Mon, 13 Apr 2009 22:32:11 +0000 http://damieng.com/blog/2009/04/12/linq-to-sql-tips-and-tricks-2#comment-14652 Brad Abrams (and the .NET team) recommends people don't implement ICloneable: http://blogs.msdn.com/brada/archive/2003/04/09/49935.aspx Brad Abrams (and the .NET team) recommends people don’t implement ICloneable:
http://blogs.msdn.com/brada/archive/2003/04/09/49935.aspx

]]> By: Dew Drop - April 13, 2009 | Alvin Ashcraft's Morning Dew http://damieng.com/blog/2009/04/12/linq-to-sql-tips-and-tricks-2#comment-14605 Dew Drop - April 13, 2009 | Alvin Ashcraft's Morning Dew Mon, 13 Apr 2009 12:05:55 +0000 http://damieng.com/blog/2009/04/12/linq-to-sql-tips-and-tricks-2#comment-14605 [...] LINQ to SQL tips and tricks #2 (Damien Guard) [...] [...] LINQ to SQL tips and tricks #2 (Damien Guard) [...]

]]> By: Steve http://damieng.com/blog/2009/04/12/linq-to-sql-tips-and-tricks-2#comment-14599 Steve Mon, 13 Apr 2009 11:20:31 +0000 http://damieng.com/blog/2009/04/12/linq-to-sql-tips-and-tricks-2#comment-14599 I honestly read the first line as "when LINQ to SQL doesn't want to cock up the TSQL" and thought wow, that's a divergence from the new professional style :) I guess that says more about me as a reader... I honestly read the first line as “when LINQ to SQL doesn’t want to cock up the TSQL” and thought wow, that’s a divergence from the new professional style :) I guess that says more about me as a reader…

]]>