<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Top Ten New Features in Entity Framework 4.0</title>
	<atom:link href="http://blog.tonysneed.com/2009/07/09/top-ten-new-features-in-entity-framework-4-0/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.tonysneed.com/2009/07/09/top-ten-new-features-in-entity-framework-4-0/</link>
	<description>A glimpse into the lives of Tony &#38; Zuzana Sneed</description>
	<lastBuildDate>Thu, 12 Aug 2010 15:59:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Tony Sneed</title>
		<link>http://blog.tonysneed.com/2009/07/09/top-ten-new-features-in-entity-framework-4-0/#comment-265</link>
		<dc:creator>Tony Sneed</dc:creator>
		<pubDate>Tue, 13 Jul 2010 19:06:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tonysneed.com/?p=161#comment-265</guid>
		<description>@Sandy: There is a &quot;using&quot; element which can allow you to share entities in the CSDL between models (perhaps what you refer to as &quot;manually hack&quot; the XML files.  Sadly, doing this will disable the designer support, forcing you to hand edit the XML for any future changes -- which is not something I recommend.  So in the meantime, the recommended approach is to duplicate common tables among the various sub-models, meaning you would have to update all the models if there is a change in one of the common tables.

So the answer is that EF4 does not offer any additional support in the area of large models.  For a database with 100 or more tables, you should definitely use multiple models, both for performance and maintainability.  For more information on this topic, see
http://blogs.msdn.com/adonet/archive/2008/11/24/working-with-large-models-in-entity-framework-part-1.aspx
http://blogs.msdn.com/adonet/archive/2008/11/24/working-with-large-models-in-entity-framework-part-2.aspx</description>
		<content:encoded><![CDATA[<p>@Sandy: There is a &#8220;using&#8221; element which can allow you to share entities in the CSDL between models (perhaps what you refer to as &#8220;manually hack&#8221; the XML files.  Sadly, doing this will disable the designer support, forcing you to hand edit the XML for any future changes &#8212; which is not something I recommend.  So in the meantime, the recommended approach is to duplicate common tables among the various sub-models, meaning you would have to update all the models if there is a change in one of the common tables.</p>
<p>So the answer is that EF4 does not offer any additional support in the area of large models.  For a database with 100 or more tables, you should definitely use multiple models, both for performance and maintainability.  For more information on this topic, see<br />
<a href="http://blogs.msdn.com/adonet/archive/2008/11/24/working-with-large-models-in-entity-framework-part-1.aspx" rel="nofollow">http://blogs.msdn.com/adonet/archive/2008/11/24/working-with-large-models-in-entity-framework-part-1.aspx</a><br />
<a href="http://blogs.msdn.com/adonet/archive/2008/11/24/working-with-large-models-in-entity-framework-part-2.aspx" rel="nofollow">http://blogs.msdn.com/adonet/archive/2008/11/24/working-with-large-models-in-entity-framework-part-2.aspx</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sandy</title>
		<link>http://blog.tonysneed.com/2009/07/09/top-ten-new-features-in-entity-framework-4-0/#comment-264</link>
		<dc:creator>Sandy</dc:creator>
		<pubDate>Tue, 13 Jul 2010 07:20:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tonysneed.com/?p=161#comment-264</guid>
		<description>Hi All,

One thing I was hoping to see on the top 10 list was an improvment to how EF copes with large models.

We have 600+ tables and don’t want to have all 600 in the one model. It would make sense to break our model into multiple sub-models and have a common model for shared tables such as a Users table which would be used in most sub-models. But you can’t reference models in your models. The work-around for this is to add the common tables to each sub-model. If a common table changes you need to update it in each model. Another work-around was to manually hack the XML files but this detracts from the user experience.

Does EF4 improve support for this scenario?

Cheers,
Sandy.</description>
		<content:encoded><![CDATA[<p>Hi All,</p>
<p>One thing I was hoping to see on the top 10 list was an improvment to how EF copes with large models.</p>
<p>We have 600+ tables and don’t want to have all 600 in the one model. It would make sense to break our model into multiple sub-models and have a common model for shared tables such as a Users table which would be used in most sub-models. But you can’t reference models in your models. The work-around for this is to add the common tables to each sub-model. If a common table changes you need to update it in each model. Another work-around was to manually hack the XML files but this detracts from the user experience.</p>
<p>Does EF4 improve support for this scenario?</p>
<p>Cheers,<br />
Sandy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Wassermann</title>
		<link>http://blog.tonysneed.com/2009/07/09/top-ten-new-features-in-entity-framework-4-0/#comment-135</link>
		<dc:creator>Mike Wassermann</dc:creator>
		<pubDate>Wed, 26 Aug 2009 13:59:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tonysneed.com/?p=161#comment-135</guid>
		<description>After installing SP 3 for XP the EF designer won&#039;t load, what can I do?

Thanks
Mike</description>
		<content:encoded><![CDATA[<p>After installing SP 3 for XP the EF designer won&#8217;t load, what can I do?</p>
<p>Thanks<br />
Mike</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Learning resources for Entity Framework 4.0 new features &#171; Bogdan Brinzarea&#8217;s blog</title>
		<link>http://blog.tonysneed.com/2009/07/09/top-ten-new-features-in-entity-framework-4-0/#comment-134</link>
		<dc:creator>Learning resources for Entity Framework 4.0 new features &#171; Bogdan Brinzarea&#8217;s blog</dc:creator>
		<pubDate>Wed, 05 Aug 2009 09:13:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tonysneed.com/?p=161#comment-134</guid>
		<description>[...] http://blog.tonysneed.com/?p=161 [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://blog.tonysneed.com/?p=161" rel="nofollow">http://blog.tonysneed.com/?p=161</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony and Zuzana&#8217;s World &#187; Who is Improving LINQ to SQL? Plinqo by Code Smith!</title>
		<link>http://blog.tonysneed.com/2009/07/09/top-ten-new-features-in-entity-framework-4-0/#comment-133</link>
		<dc:creator>Tony and Zuzana&#8217;s World &#187; Who is Improving LINQ to SQL? Plinqo by Code Smith!</dc:creator>
		<pubDate>Wed, 05 Aug 2009 03:10:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tonysneed.com/?p=161#comment-133</guid>
		<description>[...] SQL for real-world applications, especially since Microsoft has left it to languish in favor of the new version of the Entity Framework slated for release with .NET 4.0 and Visual Studio 2010. Nevertheless, I have a consulting client, [...]</description>
		<content:encoded><![CDATA[<p>[...] SQL for real-world applications, especially since Microsoft has left it to languish in favor of the new version of the Entity Framework slated for release with .NET 4.0 and Visual Studio 2010. Nevertheless, I have a consulting client, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony</title>
		<link>http://blog.tonysneed.com/2009/07/09/top-ten-new-features-in-entity-framework-4-0/#comment-132</link>
		<dc:creator>Tony</dc:creator>
		<pubDate>Sun, 12 Jul 2009 19:53:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tonysneed.com/?p=161#comment-132</guid>
		<description>The links are working now. :)  My blog had been hacked and I couldn&#039;t log in to easily edit the post.  But that&#039;s corrected now and things are back to normal.</description>
		<content:encoded><![CDATA[<p>The links are working now. <img src='http://s.wordpress.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />   My blog had been hacked and I couldn&#8217;t log in to easily edit the post.  But that&#8217;s corrected now and things are back to normal.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: brix</title>
		<link>http://blog.tonysneed.com/2009/07/09/top-ten-new-features-in-entity-framework-4-0/#comment-131</link>
		<dc:creator>brix</dc:creator>
		<pubDate>Sun, 12 Jul 2009 16:41:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tonysneed.com/?p=161#comment-131</guid>
		<description>Hi,
Great post.By the way all the links seems to be broken.</description>
		<content:encoded><![CDATA[<p>Hi,<br />
Great post.By the way all the links seems to be broken.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bindav N Pandya</title>
		<link>http://blog.tonysneed.com/2009/07/09/top-ten-new-features-in-entity-framework-4-0/#comment-130</link>
		<dc:creator>Bindav N Pandya</dc:creator>
		<pubDate>Sun, 12 Jul 2009 06:50:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tonysneed.com/?p=161#comment-130</guid>
		<description>Great work by EF Team and ofcourse great work by Tony to categorise the top 10 New features in EF.  This EF4 is going to be mind blowing STUFF !!!</description>
		<content:encoded><![CDATA[<p>Great work by EF Team and ofcourse great work by Tony to categorise the top 10 New features in EF.  This EF4 is going to be mind blowing STUFF !!!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
