<?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: Entity Framework 4 &#8211; &#8220;Almost&#8221; POCO</title>
	<atom:link href="http://rogeralsing.com/2009/05/29/entity-framework-4-almost-poco/feed/" rel="self" type="application/rss+xml" />
	<link>http://rogeralsing.com/2009/05/29/entity-framework-4-almost-poco/</link>
	<description></description>
	<lastBuildDate>Sat, 28 Jan 2012 14:35:30 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Roger Alsing</title>
		<link>http://rogeralsing.com/2009/05/29/entity-framework-4-almost-poco/#comment-1351</link>
		<dc:creator><![CDATA[Roger Alsing]]></dc:creator>
		<pubDate>Fri, 21 Aug 2009 08:46:56 +0000</pubDate>
		<guid isPermaLink="false">http://rogeralsing.com/?p=641#comment-1351</guid>
		<description><![CDATA[@Nikola, yes i have seen it and think it is a _horrible_ approach.

This is by no means at all POCO, and nor does it support linq queries against the enum property.

The entire idea behind POCO is to let you design your model w/o caring about persistence concerns.

Since this forces you to design a certain way, this kills the value of POCO.


As for now I think that using constants in a static class is the best replacement for enums in EF4 since this supports Linq queries and will be very easy to port once we get real enum support.]]></description>
		<content:encoded><![CDATA[<p>@Nikola, yes i have seen it and think it is a _horrible_ approach.</p>
<p>This is by no means at all POCO, and nor does it support linq queries against the enum property.</p>
<p>The entire idea behind POCO is to let you design your model w/o caring about persistence concerns.</p>
<p>Since this forces you to design a certain way, this kills the value of POCO.</p>
<p>As for now I think that using constants in a static class is the best replacement for enums in EF4 since this supports Linq queries and will be very easy to port once we get real enum support.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nikola Malovic</title>
		<link>http://rogeralsing.com/2009/05/29/entity-framework-4-almost-poco/#comment-1347</link>
		<dc:creator><![CDATA[Nikola Malovic]]></dc:creator>
		<pubDate>Thu, 13 Aug 2009 19:25:35 +0000</pubDate>
		<guid isPermaLink="false">http://rogeralsing.com/?p=641#comment-1347</guid>
		<description><![CDATA[Have you seen this:

http://devtalk.dk/2009/06/18/Entity+Framework+40+Beta+1+POCO+Enum+Support.aspx]]></description>
		<content:encoded><![CDATA[<p>Have you seen this:</p>
<p><a href="http://devtalk.dk/2009/06/18/Entity+Framework+40+Beta+1+POCO+Enum+Support.aspx" rel="nofollow">http://devtalk.dk/2009/06/18/Entity+Framework+40+Beta+1+POCO+Enum+Support.aspx</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

