Comments on: Is ASP.NET Viewstate bad for SEO? http://www.keyboardface.com/archives/2007/06/13/is-aspnet-viewstate-bad-for-seo/ when you find QWERTY imprinted on your cheek - it's time to go to bed. Thu, 19 May 2011 05:13:25 +0000 hourly 1 http://wordpress.org/?v=3.4.2 By: Tom http://www.keyboardface.com/archives/2007/06/13/is-aspnet-viewstate-bad-for-seo/comment-page-1/#comment-13666 Tom Fri, 21 Sep 2007 18:37:41 +0000 http://www.keyboardface.com/archives/2007/06/13/is-aspnet-viewstate-bad-for-seo/#comment-13666 Thanks - I didn't try it so I didn't know. This should be helpful to readers. Thanks – I didn’t try it so I didn’t know. This should be helpful to readers.

]]> By: Mr Yossu http://www.keyboardface.com/archives/2007/06/13/is-aspnet-viewstate-bad-for-seo/comment-page-1/#comment-13629 Mr Yossu Thu, 20 Sep 2007 16:05:30 +0000 http://www.keyboardface.com/archives/2007/06/13/is-aspnet-viewstate-bad-for-seo/#comment-13629 Hello, Your comment about removing the runat="server" attribute to reduce viewstate size is inaccurate and can lead to all sorts of problems. Removing the runat attribute will cause any server tag to fail with an error, and will cause run time errors on normal tags that need to be accessed from server-side code. What you need to do to remove an individual control from the viewstate is to set its EnableViewState property to false. This will remove it, but leave it fully operational. This is the correct way to do it. Hello,

Your comment about removing the runat=”server” attribute to reduce viewstate size is inaccurate and can lead to all sorts of problems.

Removing the runat attribute will cause any server tag to fail with an error, and will cause run time errors on normal tags that need to be accessed from server-side code.

What you need to do to remove an individual control from the viewstate is to set its EnableViewState property to false. This will remove it, but leave it fully operational. This is the correct way to do it.

]]> By: AndrewVos http://www.keyboardface.com/archives/2007/06/13/is-aspnet-viewstate-bad-for-seo/comment-page-1/#comment-12550 AndrewVos Mon, 16 Jul 2007 19:12:53 +0000 http://www.keyboardface.com/archives/2007/06/13/is-aspnet-viewstate-bad-for-seo/#comment-12550 Hi Tom, I couldn't find any way to contact you, and was wanting to comment on your page entitled "Wordpress Permalinks in IIS using Custom 404 Redirect"... If a user browsed to page: http://url/date/post then they would get redirected to the page including the query string? So in the end the user would end up on that actual page anyway, and if they copied the link at this time then it wouldn't be the permalink. The only use for permalinks in this case is when you click the actual link on the main page? I haven't been able to test this yet, because my web host is having some problems with .asp redirects as of this time, so I'm wondering if this is the right solution for me. Hi Tom,

I couldn’t find any way to contact you, and was wanting to comment on your page entitled “WordPress Permalinks in IIS using Custom 404 Redirect”…

If a user browsed to page: http://url/date/post then they would get redirected to the page including the query string?

So in the end the user would end up on that actual page anyway, and if they copied the link at this time then it wouldn’t be the permalink.

The only use for permalinks in this case is when you click the actual link on the main page?

I haven’t been able to test this yet, because my web host is having some problems with .asp redirects as of this time, so I’m wondering if this is the right solution for me.

]]>