nhib. vs ado.net

01/15/2015 14:33 dsfkdmkfm#1

why is it that everyone is using nhib. rather than ado.net, while in my poor experience with both nhib throw way more non-sense errors while ado.net has almost the same performance, ik it may not be ORM but even as query engine it still gets the work done ?

01/15/2015 18:46 turk55#2

So you rather write everything manually then have it running automatically?

01/15/2015 23:11 .John#3

ADO.NET isn't really even an option these days... It's either EF (preferred by most devs these days - including me) and nhibernate (has been around for longer, thus may be more stable).

There's so many reasons to chose an ORM. Some of the reasons:
* It's strong typed (if used fluently), meaning you can find, refactor, etc much much easier.
* It's easy. I mean VERY easy (and safe). Look how easy it is!

Code:

 var badUsers = db.Users.Where(x => x.Email.Contains("@shit.com"));

* No more messing with strings. All done via actual code.
* Setting it up is as easy as adding the project and importing your DB (theres way too many guides out there).
* Performance is amazing for what it offers.