<?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>Playing with ASP.NET</title><link>http://blogs.msdn.com/dancre/archive/2006/12/16/playing-with-asp-net.aspx</link><description>I'm doing some ASP.NET work on my current project (more about that in the coming months). I've spent most of my life doing client side code, so it's taken me a little time to really wrap my head around what's happening with ASP.NET. It often seems like</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>What does runat="server" do for HTML controls</title><link>http://blogs.msdn.com/dancre/archive/2006/12/16/playing-with-asp-net.aspx#1311702</link><pubDate>Sun, 17 Dec 2006 20:27:19 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1311702</guid><dc:creator>Dan Crevier's Blog</dc:creator><description>&lt;p&gt;One thing I didn't fully understand when I first started using ASP.NET is exactly what runat=&amp;quot;server&amp;quot;&lt;/p&gt;
</description></item></channel></rss>