ado.net - Old-school SQL DB access versus ORM (NHibernate, EF, et al). Who wins? -
i've been successful writing own sql access code combination of stored procedures , parameterized queries , little wrapper library i've written minimize ado.net grunge. has worked me in past , i've been pretty productive it.
i'm heading new project--should put old school stuff behind me , dig orm-based solution? (i know there vast high-concepts differences between nhibernate , ef--i don't want here. sake of argument, let's lump linq old-school alternatives.) i'm looking advice on real-world application of orm type stuff against know (and know pretty well).
old-school ado.net code or orm? i'm sure there curve--does curve have roi makes things worthwhile? i'm anxious , willing learn, have deadline.
a question controversial topic.
this blog post frans bouma few years citing pros of dynamic sql (implying orms) on stored procedures sparked quite fiery flame war.
Comments
Post a Comment