tag:blogger.com,1999:blog-5763764290649132593.post8509399615475442313..comments2023-08-09T13:17:49.225+02:00Comments on CLOSED-LOOP: Bookreview: MVC4 in ActionAnonymoushttp://www.blogger.com/profile/00990537252799084615noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-5763764290649132593.post-29422746636788317552012-07-08T13:54:05.408+02:002012-07-08T13:54:05.408+02:00@Jef
I personally still prefer to use NHibernate ...@Jef<br /><br />I personally still prefer to use NHibernate because I have quite a lot of experience with NHibernate.<br /><br />But I think Microsoft has made big progress with EF and is continuing to do so.<br />I think integrating MVC with EF is just easier and a more seamless experience than integrating MVC with NHibernate. (partly because of the tooling and documentation that MS provides, but also because there is less accidental complexity involved in my opinion).<br />And EF is really starting to provide neat features with code-first, data-annotations and migrations ... of course you can get the same with NHibernate, but you have to get much more involved while the result is not necessarily better...Anonymoushttps://www.blogger.com/profile/00990537252799084615noreply@blogger.comtag:blogger.com,1999:blog-5763764290649132593.post-57251143325541803412012-07-08T11:08:53.489+02:002012-07-08T11:08:53.489+02:00Why should EF be the default choice for MVC?Why should EF be the default choice for MVC?Jef Claeshttps://www.blogger.com/profile/17313599911430422160noreply@blogger.com