<?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/"
		>
<channel>
	<title>Kommentare zu: ADO.NET Entity Framework: unexpected behaviour with MergeOptions</title>
	<atom:link href="http://blog.dynatrace.com/2009/03/11/adonet-entity-framework-unexpected-behaviour-with-mergeoptions/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.dynatrace.com/2009/03/11/adonet-entity-framework-unexpected-behaviour-with-mergeoptions/</link>
	<description></description>
	<lastBuildDate>Sat, 11 Feb 2012 09:39:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
	<item>
		<title>Von: Performance, Scalability and Architecture - Java and .NET Application Performance Management (dynaTrace Blog) &#187; Memory Leak in EntityDataSource when controlling lifetime of your ObjectContext</title>
		<link>http://blog.dynatrace.com/2009/03/11/adonet-entity-framework-unexpected-behaviour-with-mergeoptions/comment-page-1/#comment-3155</link>
		<dc:creator>Performance, Scalability and Architecture - Java and .NET Application Performance Management (dynaTrace Blog) &#187; Memory Leak in EntityDataSource when controlling lifetime of your ObjectContext</dc:creator>
		<pubDate>Tue, 12 May 2009 12:27:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dynatrace.com/?p=396#comment-3155</guid>
		<description>[...] The described approach works fine. It also allows you to use the ObjectContext across page requests. This can be useful when you don&#8217;t have data that changes frequently and if you want to save on lots of short living objects that are created when accessing the same data all over again. A description about that can be found in my recent article about the ADO.NET Entity Framework. [...]</description>
		<content:encoded><![CDATA[<p>[...] The described approach works fine. It also allows you to use the ObjectContext across page requests. This can be useful when you don&#8217;t have data that changes frequently and if you want to save on lots of short living objects that are created when accessing the same data all over again. A description about that can be found in my recent article about the ADO.NET Entity Framework. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: Simonn</title>
		<link>http://blog.dynatrace.com/2009/03/11/adonet-entity-framework-unexpected-behaviour-with-mergeoptions/comment-page-1/#comment-1535</link>
		<dc:creator>Simonn</dc:creator>
		<pubDate>Sun, 22 Mar 2009 02:33:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dynatrace.com/?p=396#comment-1535</guid>
		<description>Keep working ,great job!</description>
		<content:encoded><![CDATA[<p>Keep working ,great job!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: Msn Messenger For Java Mobile &#124; Mobile Software Java Blackberry</title>
		<link>http://blog.dynatrace.com/2009/03/11/adonet-entity-framework-unexpected-behaviour-with-mergeoptions/comment-page-1/#comment-1413</link>
		<dc:creator>Msn Messenger For Java Mobile &#124; Mobile Software Java Blackberry</dc:creator>
		<pubDate>Wed, 11 Mar 2009 06:35:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dynatrace.com/?p=396#comment-1413</guid>
		<description>[...] Performance, Scalability and Architecture - Java and .NET &#8230; [...]</description>
		<content:encoded><![CDATA[<p>[...] Performance, Scalability and Architecture &#8211; Java and .NET &#8230; [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

