<?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>Update for viewstate issues</title><link>http://blogs.msdn.com/tom/archive/2008/08/12/update-for-viewstate-issues.aspx</link><description>So a while ago I posted about how to fix the Validation of viewstate MAC failed error .&amp;#160; There is some really exciting news that is coming with Visual Studio 2008 Service Pack 1 and .NET Framework 3.5 Service Pack 1.&amp;#160; One of the improvements</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Update for viewstate issues | Easycoded</title><link>http://blogs.msdn.com/tom/archive/2008/08/12/update-for-viewstate-issues.aspx#8853024</link><pubDate>Tue, 12 Aug 2008 22:05:37 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8853024</guid><dc:creator>Update for viewstate issues | Easycoded</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://www.easycoded.com/update-for-viewstate-issues"&gt;http://www.easycoded.com/update-for-viewstate-issues&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>re: Update for viewstate issues</title><link>http://blogs.msdn.com/tom/archive/2008/08/12/update-for-viewstate-issues.aspx#8855713</link><pubDate>Wed, 13 Aug 2008 06:45:04 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8855713</guid><dc:creator>Vesta</dc:creator><description>&lt;p&gt;i had this error in vs 2005 what about that?&lt;/p&gt;</description></item><item><title>re: Update for viewstate issues</title><link>http://blogs.msdn.com/tom/archive/2008/08/12/update-for-viewstate-issues.aspx#8859469</link><pubDate>Wed, 13 Aug 2008 19:59:27 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8859469</guid><dc:creator>Tom</dc:creator><description>&lt;p&gt;Vesta,&lt;/p&gt;
&lt;p&gt;For VS 2005, you will have to use the workarounds documented on the previous post.&lt;/p&gt;
</description></item><item><title>re: Update for viewstate issues</title><link>http://blogs.msdn.com/tom/archive/2008/08/12/update-for-viewstate-issues.aspx#8859919</link><pubDate>Wed, 13 Aug 2008 21:11:15 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8859919</guid><dc:creator>Francois Ward</dc:creator><description>&lt;p&gt;Oh oh, thats interesting... I had missed that other post detailing the issue.&lt;/p&gt;
&lt;p&gt;I had that issue before (when I was explicitely encrypting viewstate, not because I was using a datakey), and had successfully figured out the issue.&lt;/p&gt;
&lt;p&gt;However, I didn't quite understand WHY it happened (since ViewState is one of the first fields in the page). I wasn't aware that encryption of viewstate added a field near the bottom, never notice...&lt;/p&gt;
&lt;p&gt;Now -that- explains it. Glad that its fixed in SP1.&lt;/p&gt;</description></item><item><title>re: Update for viewstate issues</title><link>http://blogs.msdn.com/tom/archive/2008/08/12/update-for-viewstate-issues.aspx#8860383</link><pubDate>Wed, 13 Aug 2008 22:29:33 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8860383</guid><dc:creator>TheXenocide</dc:creator><description>&lt;p&gt;I'm glad you commented on this; I didn't know you had posted on this before but the information could be very useful to us at work. Thanks!&lt;/p&gt;</description></item><item><title>re: Update for viewstate issues</title><link>http://blogs.msdn.com/tom/archive/2008/08/12/update-for-viewstate-issues.aspx#8876307</link><pubDate>Mon, 18 Aug 2008 15:00:23 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8876307</guid><dc:creator>Mike</dc:creator><description>&lt;p&gt;This update has also effected the rendering of said tags in projects compiled for the 2.0 framework. I'm quite surprised to see the update effect NET 2.0, we now have a little issue to figure out. &lt;/p&gt;
&lt;p&gt;Our developers use VS 2008 targeting NET 2 framework but production has not yet 'approved' nor do we have a need for NET 3.5. What was done to 2.0? How do we get this fix to production?&lt;/p&gt;</description></item><item><title>re: Update for viewstate issues</title><link>http://blogs.msdn.com/tom/archive/2008/08/12/update-for-viewstate-issues.aspx#8876545</link><pubDate>Mon, 18 Aug 2008 17:44:51 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8876545</guid><dc:creator>Mike</dc:creator><description>&lt;p&gt;After some investigation it appears that the 3.5 SP1 includes NET 2.0 SP2. I can find no info on a standalone NET 2.0 SP2 install or how you might apply only the 2.0 SP2 to a non 3.5 system.&lt;/p&gt;</description></item><item><title>ViewState validation troubles?</title><link>http://blogs.msdn.com/tom/archive/2008/08/12/update-for-viewstate-issues.aspx#9250999</link><pubDate>Wed, 24 Dec 2008 01:06:32 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9250999</guid><dc:creator>Never doubt thy debugger</dc:creator><description>&lt;p&gt;If you work with web sites in a complex/multi server environment you might be familiar with this error&lt;/p&gt;
</description></item><item><title>re: Update for viewstate issues</title><link>http://blogs.msdn.com/tom/archive/2008/08/12/update-for-viewstate-issues.aspx#9388823</link><pubDate>Mon, 02 Feb 2009 02:07:19 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9388823</guid><dc:creator>Paul</dc:creator><description>&lt;p&gt;I'm having this exact issue on a 3.5 sp1 site when there's only 1 label &amp;nbsp;on the form (in an updatepanel) The updates itself every 5 secs with the current time. The error starts occuring after approx. 2:50 minutes. I'll follow up with more info...&lt;/p&gt;</description></item><item><title>re: Update for viewstate issues</title><link>http://blogs.msdn.com/tom/archive/2008/08/12/update-for-viewstate-issues.aspx#9730888</link><pubDate>Fri, 12 Jun 2009 09:54:20 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9730888</guid><dc:creator>vijaykumar_gupta</dc:creator><description>&lt;p&gt;I have same problem in .NET farme work 3.5 with service pack 1 while updating the page 's control value with postback.&lt;/p&gt;
&lt;p&gt;When erver i am trying to update grid through the update link i am getting this message........&lt;/p&gt;
&lt;p&gt;&amp;quot;Microsoft JScript runtime error: Sys.WebForms.PageRequestManagerServerErrorException: Validation of viewstate MAC failed. If this application is hosted by a Web Farm or cluster, ensure that &amp;lt;machineKey&amp;gt; configuration specifies the same validationKey and validation algorithm. AutoGenerate cannot be used in a cluster.&amp;quot;&lt;/p&gt;
&lt;p&gt;While i have update pane on the page and trying to update the grid without postback.&lt;/p&gt;
&lt;p&gt;Also i have implemented URL Rewring in my web application.&lt;/p&gt;
&lt;p&gt;Please &amp;nbsp;help me.&lt;/p&gt;
&lt;p&gt;Thanks&lt;/p&gt;</description></item></channel></rss>