This question seemed to diverge off into the Linq direction, but I didn't see anyone confirm or deny if nHibernate is the way to go or not.
Some time ago I wrote an app and used Linq to SQL and was really happy with how simple it made things. Then there was the on again off again future of Linq to SQL (and to be honest I'm not sure what it's current future is). The complexity and immaturity of EF and the minefield of alternatives makes for a good question. I want something that was simple like Linq to SQL. Drag and drop the data object onto a form and it wires it up for me, giving me POCOs to code against. I'll be needing to decide what to invest my time into. latest EF? nHibernate? llbgen? Any further comments on what to use? I know (and love) Linq. I'm not an expert but with LinqPad and Resharper I get by. Linq is amazing. On Tue, Jul 13, 2010 at 11:18 PM, Les Hughes <l...@datarev.com.au> wrote: > > Hi All, > > I'm about to start working on a mid-sized data-centric app (accounting > area) which is mostly just lots of forms which display data, edit/write > data, and then spitting out some pretty reports, etc with the data sitting > in SQL Server. (Think of old-school MSaccess apps) > > Wanting to avoid as much SQL plumbing as I can, I'm looking to use > nHibernate for a lot of the lifting, but haven't had a chance to look around > at perhaps some better packages/practices/etc which exist. > > At this stage I have spent near zero time with Linq, and have only heard of > a few other packages in passing (Fluent/Active Record/etc), and am wondering > what (if anything) I should spend some time looking in to. > > My query is: > > - Is nHibernate still the way to go? What do the rest of the .NETters use > for their data access layers? And why? Is Linq worth the learning curve? > > Any feedback would be greatly appreciated. > > Thanks in advance, > -- > Les Hughes > l...@datarev.com.au >
