Comments for Sidar Ok Technical Blog ! http://www.sidarok.com/web/blog still believes in coding to make dreams come true Thu, 20 Nov 2008 20:55:47 +0000 http://wordpress.org/?v=2.2.3 Comment on Achieving POCO s in Linq to SQL by Matt http://www.sidarok.com/web/blog/content/2008/10/14/achieving-poco-s-in-linq-to-sql.html#comment-3834 Matt Wed, 19 Nov 2008 08:36:06 +0000 http://www.sidarok.com/web/blog/content/2008/10/14/achieving-poco-s-in-linq-to-sql.html#comment-3834 Hi Sidar, I've been using your blog post as a guide to implementing POCO with LINQToSQL in my own solution, but am having some troubles with nested list. Would it be possible for you to have a look at my StackOverflow question and pass on any guidance you can? It would be muchly appreciated as I'm now at the point of pulling my hair out. Regards, Matt http://stackoverflow.com/questions/298162/help-needed-for-linq-to-sql-operations-insertupdate-with-nested-pocos Hi Sidar,

I’ve been using your blog post as a guide to implementing POCO with LINQToSQL in my own solution, but am having some troubles with nested list.

Would it be possible for you to have a look at my StackOverflow question and pass on any guidance you can?

It would be muchly appreciated as I’m now at the point of pulling my hair out.

Regards,

Matt

http://stackoverflow.com/questions/298162/help-needed-for-linq-to-sql-operations-insertupdate-with-nested-pocos

]]> Comment on Linq to SQL Wish List by Kian http://www.sidarok.com/web/blog/content/2008/06/04/linq-to-sql-wish-list.html#comment-2850 Kian Tue, 04 Nov 2008 17:41:55 +0000 http://www.sidarok.com/web/blog/content/2008/06/04/linq-to-sql-wish-list.html#comment-2850 Keep a good work man!, Keep a good work man!,

]]> Comment on Lazy Loading with Linq to SQL POCO s by Sidar Ok http://www.sidarok.com/web/blog/content/2008/10/29/lazy-loading-with-linq-to-sql-poco-s.html#comment-2653 Sidar Ok Fri, 31 Oct 2008 00:16:32 +0000 http://www.sidarok.com/web/blog/content/2008/10/29/lazy-loading-with-linq-to-sql-poco-s.html#comment-2653 No problem, ask any questions you come up with. Here are the sources : http://www.sidarok.com/files/LazyLoadingPocoSample.rar I intentionally left it dirty to show the paths I tried to go down. Hope it helps. No problem, ask any questions you come up with. Here are the sources : http://www.sidarok.com/files/LazyLoadingPocoSample.rar

I intentionally left it dirty to show the paths I tried to go down. Hope it helps.

]]> Comment on Lazy Loading with Linq to SQL POCO s by Russ Painter http://www.sidarok.com/web/blog/content/2008/10/29/lazy-loading-with-linq-to-sql-poco-s.html#comment-2629 Russ Painter Thu, 30 Oct 2008 08:25:42 +0000 http://www.sidarok.com/web/blog/content/2008/10/29/lazy-loading-with-linq-to-sql-poco-s.html#comment-2629 Thanks. Although I think I need to read that a couple more times. Do you have source code to share? Thanks. Although I think I need to read that a couple more times. Do you have source code to share?

]]> Comment on Achieving POCO s in Linq to SQL by Lazy Loading with Linq to SQL POCO s | Sidar Ok Technical Blog ! http://www.sidarok.com/web/blog/content/2008/10/14/achieving-poco-s-in-linq-to-sql.html#comment-2568 Lazy Loading with Linq to SQL POCO s | Sidar Ok Technical Blog ! Wed, 29 Oct 2008 01:41:44 +0000 http://www.sidarok.com/web/blog/content/2008/10/14/achieving-poco-s-in-linq-to-sql.html#comment-2568 [...] About Sidar Sidar Ok Technical Blog ! « Achieving POCO s in Linq to SQL [...] […] About Sidar Sidar Ok Technical Blog ! « Achieving POCO s in Linq to SQL […]

]]> Comment on Achieving POCO s in Linq to SQL by Sidar Ok http://www.sidarok.com/web/blog/content/2008/10/14/achieving-poco-s-in-linq-to-sql.html#comment-2508 Sidar Ok Mon, 27 Oct 2008 10:50:56 +0000 http://www.sidarok.com/web/blog/content/2008/10/14/achieving-poco-s-in-linq-to-sql.html#comment-2508 Hi Russ, Lately I have been spending a lot of time with that and bumping into the limitations of L2S development discrepencies. I will also discuss them in another blog post, but bear with me, I am close to there :) Hi Russ,

Lately I have been spending a lot of time with that and bumping into the limitations of L2S development discrepencies. I will also discuss them in another blog post, but bear with me, I am close to there :)

]]> Comment on Achieving POCO s in Linq to SQL by Russ Painter http://www.sidarok.com/web/blog/content/2008/10/14/achieving-poco-s-in-linq-to-sql.html#comment-2505 Russ Painter Mon, 27 Oct 2008 09:45:34 +0000 http://www.sidarok.com/web/blog/content/2008/10/14/achieving-poco-s-in-linq-to-sql.html#comment-2505 Still anxiously awaiting your lazy loading solution. Still anxiously awaiting your lazy loading solution.

]]> Comment on Achieving POCO s in Linq to SQL by Sidar Ok http://www.sidarok.com/web/blog/content/2008/10/14/achieving-poco-s-in-linq-to-sql.html#comment-2411 Sidar Ok Fri, 24 Oct 2008 21:52:38 +0000 http://www.sidarok.com/web/blog/content/2008/10/14/achieving-poco-s-in-linq-to-sql.html#comment-2411 @Corey, Yes I did check out - It is a code generator, which generates another layer of mapping. Please see my response in the above comments to Rob on another layer of mapping. On top of them, EF is already very heavy with 2 levels of mapping, adding 3 rd level to this stack where I just need 1 level is an overkill and overhead. It is not a solution to the problem, it is just a *workaround*. And a work around that has all the problems inherently from code generation perspective, e.g source control nightmares, maintaining untested mappings, loads of classes that are not used, being bound to the generation technology etc. The more layers you are away from ORM's Context, less you get the goodies of it or depend on generation to get them - why would I, when I don't need to increase the distance ? I still need to regen my Adapter layer and Proxies for lazy loading when a change occurs in the db, it is inevitable. So no positives on that side either. (btw, the amount of mapping you need to regen when db model changes in EF is already tremendous, not to mention the poco adapter). L2S is very easy and provides lots of flexibility in this context, does what it needs to, doesn't what it can't do good. On the other hand, I will keep an eye on your blog and already looking forward to the posts. Thanks for the comment. @Corey,

Yes I did check out - It is a code generator, which generates another layer of mapping. Please see my response in the above comments to Rob on another layer of mapping.

On top of them, EF is already very heavy with 2 levels of mapping, adding 3 rd level to this stack where I just need 1 level is an overkill and overhead. It is not a solution to the problem, it is just a *workaround*. And a work around that has all the problems inherently from code generation perspective, e.g source control nightmares, maintaining untested mappings, loads of classes that are not used, being bound to the generation technology etc. The more layers you are away from ORM’s Context, less you get the goodies of it or depend on generation to get them - why would I, when I don’t need to increase the distance ?

I still need to regen my Adapter layer and Proxies for lazy loading when a change occurs in the db, it is inevitable. So no positives on that side either. (btw, the amount of mapping you need to regen when db model changes in EF is already tremendous, not to mention the poco adapter). L2S is very easy and provides lots of flexibility in this context, does what it needs to, doesn’t what it can’t do good.

On the other hand, I will keep an eye on your blog and already looking forward to the posts. Thanks for the comment.

]]> Comment on Achieving POCO s in Linq to SQL by Corey Gaudin http://www.sidarok.com/web/blog/content/2008/10/14/achieving-poco-s-in-linq-to-sql.html#comment-2401 Corey Gaudin Fri, 24 Oct 2008 17:05:40 +0000 http://www.sidarok.com/web/blog/content/2008/10/14/achieving-poco-s-in-linq-to-sql.html#comment-2401 Hey Sidar, Have you checked out EFPocoAdapter? Its something (http://blogs.msdn.com/jkowalski/archive/2008/09/09/persistence-ignorance-poco-adapter-for-entity-framework-v1.aspx) that will allow you to utilize EF and work with POCO objects. I have successfully used in in a number of projects and architectures. I am planning on doing a 6 Series blog post on how to use it and setup, etc. Give it a shot, and be on a lookout for my blog posts on this. It just seems that once you have it setup, there is no need to manually regen xml or code files by using this approach. Hey Sidar,

Have you checked out EFPocoAdapter? Its something (http://blogs.msdn.com/jkowalski/archive/2008/09/09/persistence-ignorance-poco-adapter-for-entity-framework-v1.aspx) that will allow you to utilize EF and work with POCO objects. I have successfully used in in a number of projects and architectures. I am planning on doing a 6 Series blog post on how to use it and setup, etc. Give it a shot, and be on a lookout for my blog posts on this.

It just seems that once you have it setup, there is no need to manually regen xml or code files by using this approach.

]]> Comment on 10 Tips to Improve your LINQ to SQL Application Performance by Panfila http://www.sidarok.com/web/blog/content/2008/05/02/10-tips-to-improve-your-linq-to-sql-application-performance.html#comment-2363 Panfila Thu, 23 Oct 2008 14:58:38 +0000 http://www.sidarok.com/web/blog/content/2008/05/02/10-tips-to-improve-your-linq-to-sql-application-performance.html#comment-2363 Well said. Well said.

]]>