﻿<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://developers.de/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>How to change T4 POCO Templates of EF 4 for WCF?</title><link />http://developers.de/blogs/damir_dobric/archive/2010/04/25/how-to-change-t4-poco-templates-of-ef-4-for-wcf.aspx<description>Thanks to .NET 3.5 SP1 one class does not require to have DataContract attribute to be serializable by WCF. This is fine, but when building real SOA applications, there are always something special you will need. Such special things could be manually</description><dc:language>en</dc:language><generator>CommunityServer 2008 SP1 (Build: 30619.63)</generator><item><title>re: How to change T4 POCO Templates of EF 4 for WCF?</title><link />http://developers.de/blogs/damir_dobric/archive/2010/04/25/how-to-change-t4-poco-templates-of-ef-4-for-wcf.aspx#11567<pubdate>Sun, 25 Apr 2010 13:16:46 GMT</pubdate><guid ispermalink="false">7e491611-45ad-4dae-a68f-c4cb64439510:11567</guid><dc:creator>Christian Weyer</dc:creator><description>&lt;p&gt;You are talking about &amp;quot;Real SOA&amp;quot;... then why in the first place care about exposing EF4-based entities in the service facade?&lt;/p&gt;
&lt;p&gt;Confused...&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://developers.de/aggbug.aspx?PostID=11567" width="1" height="1"&gt;</description></item></channel></rss>