I guess there was a misunderstanding. I tried to say that Microsoft didn't kill Linq to Sql for no apparent reason, but to promote the EF that is their best ORM solution at this point, trying to illustrate that there is something besides linq to sql from the ms stack. I made that comment since nobody mentioned EF.
Also, I can't really see your argument about open sourceIf I have the source to something, I can make those updates myself. Or I can pay someone to do so. With Mirosoft's framework that's not an option, since I can't access their code and continue work. I made a pretty huge investment into the Linq to Sql stack some time back, and have been coding around framework shortcomings ever since. greetings Daniel On Sun, May 31, 2009 at 5:20 PM, James Curran <[email protected]>wrote: > > On Thu, May 28, 2009 at 5:08 AM, Daniel Hölbling <[email protected]> > wrote: > > Only Linq to Sql is dead, Microsoft killed it > > That not particularly relevant. Yes, MS has said that there won't be > anymore updates to Linq2Sql--- However, AR & NH are open-source > projects --- Updates to them can stop at any moment without any > notice. > > > -- > 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 -~----------~----~----~----~------~----~------~--~---
