<?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>Talking Points: ADO.NET Dynamic Data</title><link>http://blogs.msdn.com/b/publicsector/archive/2009/02/10/talking-points-ado-net-dynamic-data.aspx</link><description>In this age of doing more with less, government software developers are constantly having to shrink the “time-to-release” and in some instances even compromise quality. Development teams have to content with picking up new skills/technologies, while maintaining</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>Public Sector Developer Weblog : Talking Points: ADO.NET Dynamic Data</title><link>http://blogs.msdn.com/b/publicsector/archive/2009/02/10/talking-points-ado-net-dynamic-data.aspx#9411765</link><pubDate>Wed, 11 Feb 2009 04:39:33 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9411765</guid><dc:creator>DotNetShoutout</dc:creator><description>&lt;p&gt;Thank you for submitting this cool story - Trackback from DotNetShoutout&lt;/p&gt;
&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9411765" width="1" height="1"&gt;</description></item></channel></rss>