<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/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>So Special - InitializeService in ADO.NET Data Services</title><link>http://blogs.msdn.com/marcelolr/archive/2008/06/16/so-special-initializeservice-in-ado-net-data-services.aspx</link><description>In this post I'd like to talk a bit about the InitializeService method that ADO.NET Data Service writers should implement on their services. Usually this would have been a virtual method that developers could override, however it was important to stress</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Why is my ADO.NET Data Service empty?</title><link>http://blogs.msdn.com/marcelolr/archive/2008/06/16/so-special-initializeservice-in-ado-net-data-services.aspx#8612079</link><pubDate>Tue, 17 Jun 2008 20:52:22 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8612079</guid><dc:creator>Marcelo's WebLog</dc:creator><description>&lt;p&gt;Very commonly, this has to do with how the service was initialized . The service configuration allows&lt;/p&gt;
</description></item><item><title>Mutability in the .NET Framework</title><link>http://blogs.msdn.com/marcelolr/archive/2008/06/16/so-special-initializeservice-in-ado-net-data-services.aspx#8618557</link><pubDate>Thu, 19 Jun 2008 00:54:40 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8618557</guid><dc:creator>Marcelo's WebLog</dc:creator><description>&lt;p&gt;Long on prose and short on code, this post just explores some patterns involving mutable/immutable objects&lt;/p&gt;
</description></item></channel></rss>