Comments on: One Softie’s experience http://wagnerblog.com/2007/02/one-softies-experience/ Development Ideas and Ramblings Tue, 14 Oct 2008 20:14:10 -0700 http://wordpress.org/?v=2.8.4 hourly 1 By: wagnerblog.com » ScottGu bucks the trend and runs the risk of….. succeeding ! http://wagnerblog.com/2007/02/one-softies-experience/comment-page-1/#comment-493 wagnerblog.com » ScottGu bucks the trend and runs the risk of….. succeeding ! Sun, 02 Dec 2007 18:41:13 +0000 http://wagnerblog.com/?p=785#comment-493 [...] into System.Web, is something that Dan and I have been using for quite some time. Our framework PathNET has had MVC for almost 2 years. Thanks to Dan mostly (gotta give the guy some props). So having MVC [...] [...] into System.Web, is something that Dan and I have been using for quite some time. Our framework PathNET has had MVC for almost 2 years. Thanks to Dan mostly (gotta give the guy some props). So having MVC [...]

]]> By: Thomas http://wagnerblog.com/2007/02/one-softies-experience/comment-page-1/#comment-492 Thomas Fri, 23 Mar 2007 16:51:19 +0000 http://wagnerblog.com/?p=785#comment-492 jc -- I know what you mean about filtering being hard to understand with llblgen. But I have to say in its defense it is based on solid object structures whereas linq ends up using some sort of pseudo sql declarative code which is problematic when you get into more complex scenarios. First its a problem because it doesnt seem to adhere to proper sql standards. Secondly its an even bigger issue when it comes time to debug because it introduces declarative code that is not compiler checked or anything. Lets say you have a complex filter - in linq you may not know its broken or whats broken because the logic is declarative - while other systems similar to llblgen can quickly pinpoint that issue. jc — I know what you mean about filtering being hard to understand with llblgen. But I have to say in its defense it is based on solid object structures whereas linq ends up using some sort of pseudo sql declarative code which is problematic when you get into more complex scenarios. First its a problem because it doesnt seem to adhere to proper sql standards. Secondly its an even bigger issue when it comes time to debug because it introduces declarative code that is not compiler checked or anything. Lets say you have a complex filter – in linq you may not know its broken or whats broken because the logic is declarative – while other systems similar to llblgen can quickly pinpoint that issue.

]]> By: jc http://wagnerblog.com/2007/02/one-softies-experience/comment-page-1/#comment-491 jc Tue, 20 Mar 2007 19:40:28 +0000 http://wagnerblog.com/?p=785#comment-491 According to ScottGu, linq has all sorts of great hooks to allow frameworks to work with it. SQLMetal will compete, but LINQ seems to just be declarative language that you can hook into with any framework. For example Linq on an XML file (XLinq) produces different results than Linq on a data file (DLinq). Hopefully LLBLGen Pro will update the framework to work seemlessly with LINQ (LLBLinq) and the language enhancements of C# 3.0. Using blocks and linq features could seriously fix a lot of the problems with LLBL (their Filtering and Sorting object model is really hard to write and maintain). According to ScottGu, linq has all sorts of great hooks to allow frameworks to work with it. SQLMetal will compete, but LINQ seems to just be declarative language that you can hook into with any framework. For example Linq on an XML file (XLinq) produces different results than Linq on a data file (DLinq).

Hopefully LLBLGen Pro will update the framework to work seemlessly with LINQ (LLBLinq) and the language enhancements of C# 3.0. Using blocks and linq features could seriously fix a lot of the problems with LLBL (their Filtering and Sorting object model is really hard to write and maintain).

]]>