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 production server so you’d at least stand a chance of figuring out which page had the biggest. Fortunately, I was able to come up with a nice solution that should be trivial for you to deploy. Read all about it my latest Bugslayer column at the MSDN Magazine web site: