<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://www.wintellect.com/CS/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>Keeping an Eye on View State</title><link>http://www.wintellect.com/CS/blogs/jrobbins/archive/2007/10/12/keeping-an-eye-on-view-state.aspx</link><description>View State is the silent performance killer for any ASP.NET application. I've seen numerous nasty problems related to view states being far larger than anyone could have hoped to guess. My goal was to find an easy way to keep track of view state on a</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61129.2)</generator><item><title>Interesting Finds: October 12, 2007</title><link>http://www.wintellect.com/CS/blogs/jrobbins/archive/2007/10/12/keeping-an-eye-on-view-state.aspx#4033</link><pubDate>Fri, 12 Oct 2007 14:24:16 GMT</pubDate><guid isPermaLink="false">c9b5046a-91b6-4822-a57a-d848b8cb6435:4033</guid><dc:creator>Jason Haley</dc:creator><description /></item></channel></rss>