<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: The ADO.NET Entity Framework vs. NHibernate and Other ORMs</title>
	<atom:link href="http://blogs.teamb.com/craigstuntz/2008/07/17/37825/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.teamb.com/craigstuntz/2008/07/17/37825/</link>
	<description>C# • Entity Framework • Functional Programming • MVC • Web</description>
	<pubDate>Sat, 11 Feb 2012 15:34:33 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: ursri</title>
		<link>http://blogs.teamb.com/craigstuntz/2008/07/17/37825/#comment-13285</link>
		<dc:creator>ursri</dc:creator>
		<pubDate>Tue, 12 Jan 2010 07:02:37 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.teamb.com/craigstuntz/2008/07/17/37825#comment-13285</guid>
		<description>How about comparision with nHydrate?
&lt;blockquote&gt;&lt;i&gt;&lt;b&gt;Response:&lt;/b&gt;I think it would be an apples and oranges comparison. In other words, something like nHydrate is really only useful for NHibernate (not surprising, since that's what it was designed for). Most of what it does I would do completely differently in the Entity Framework, mostly using LINQ to Entities.&lt;/i&gt;&lt;/blockquote&gt;</description>
		<content:encoded><![CDATA[<p>How about comparision with nHydrate?</p>
<blockquote><p><i><b>Response:</b>I think it would be an apples and oranges comparison. In other words, something like nHydrate is really only useful for NHibernate (not surprising, since that&#8217;s what it was designed for). Most of what it does I would do completely differently in the Entity Framework, mostly using LINQ to Entities.</i></p></blockquote>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Hunsaker</title>
		<link>http://blogs.teamb.com/craigstuntz/2008/07/17/37825/#comment-4974</link>
		<dc:creator>Jeff Hunsaker</dc:creator>
		<pubDate>Fri, 27 Mar 2009 18:03:26 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.teamb.com/craigstuntz/2008/07/17/37825#comment-4974</guid>
		<description>Nice write-up, Craig. I'm looking forward to EF maturing as a solution. It feels very 1.0 now and too "heavy" for some if not a lot of our typical solutions. But, it's encouraging to see Microsoft make a play in the ORM space and not get bullied into following a particular design pattern. I think EF will be a solid solution in the long run.</description>
		<content:encoded><![CDATA[<p>Nice write-up, Craig. I&#8217;m looking forward to EF maturing as a solution. It feels very 1.0 now and too "heavy" for some if not a lot of our typical solutions. But, it&#8217;s encouraging to see Microsoft make a play in the ORM space and not get bullied into following a particular design pattern. I think EF will be a solid solution in the long run.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Günter Zöchbauer</title>
		<link>http://blogs.teamb.com/craigstuntz/2008/07/17/37825/#comment-3728</link>
		<dc:creator>Günter Zöchbauer</dc:creator>
		<pubDate>Wed, 06 Aug 2008 08:39:32 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.teamb.com/craigstuntz/2008/07/17/37825#comment-3728</guid>
		<description>Thanks für this helpful article.

EF is the subject of my bachelors thesis.
I come to a similar conclusion so far.

Imho currently EF can be seen as prototype which will eventually become a mature product sometimes.</description>
		<content:encoded><![CDATA[<p>Thanks für this helpful article.</p>
<p>EF is the subject of my bachelors thesis.<br />
I come to a similar conclusion so far.</p>
<p>Imho currently EF can be seen as prototype which will eventually become a mature product sometimes.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

