Wrong answer, that's a bit harsh :) - I was just trying to clarify what they were referring to as "Linq" (because it obviously wasn't the blanket concept of a language integrated query) - I wasn't attempting to answer the question... I have actually seen the odd developer using Linq for objects blindly on results coming from some a legacy DAO they've written *shudder* where to their mind they are doing "Linq", but only by name rather then in spirit. On Thu, May 28, 2009 at 4:10 PM, Markus Zywitza <[email protected]>wrote:
> > Wrong question, wrong answer... > > It's neither Linq2SQL nor Linq2objects. L2SQL is not only LINQ but a > LINQ provider on top of MS mapping wizards. LINQ2AR is a wrapper > around LINQ2NH (or NHLinq), which are LINQ providers for NHibernate. > In the end, it means that you can use ActiveRecord with the powers of > NHibernate and the IntelliSense of a LINQ-Provider. > > -Markus > > 2009/5/28 James Curran <[email protected]>: > > > > On Wed, May 27, 2009 at 10:13 PM, Alex Henderson <[email protected]> > wrote: > >> When you say Linq, are you referring to Linq2Sql or Linq2objects? > > > > Linq2Sql (I'm using Linq2Objects also, but I figured that's > > irrelevant to the topic) > > > > -- > > Truth, > > James > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en -~----------~----~----~----~------~----~------~--~---
