Comments on Project 31-A: Error : /ScriptResource.axd : Invalid viewstate.

Thanks man it worked.

2011-02-09T13:18:24.736-08:00

Thanks man it worked.

Hi, Is this problem related to the "the 4kb ...

2010-06-16T11:53:20.982-07:00

Hi,

Is this problem related to the "the 4kb bug"?
Is this fixed in the IE8 Cumulative Update (KB980182)?

Thanks,
Ariel

Exactly what I was looking for Thanks =)

2010-01-12T08:27:21.996-08:00

Exactly what I was looking for

Thanks =)

I suggest looking here: http://blogs.msdn.com/iei...

2009-10-05T07:58:07.079-07:00

I suggest looking here:

http://blogs.msdn.com/ieinternals/archive/2009/07/27/Bugs-in-the-IE8-Lookahead-Downloader.aspx

End of the day, the fix mentioned above isn't a global solution for anyone. Yes, you will have to rollback your CSS and retro-fit, but in addition, this doesn't cover all the possible conditions where the IE 8 parser will restart.

For example, if you have added an out of the box Master Page to your .Net application you have the vanilla namespace:

xmlns="http://www.w3.org/1999/xhtml"

most likely, well this will cause the parser to restart as well. There is still no exhaustive list from MS that covers all parser restart scenerios.

So I'd advise reviewing all resources and taking suggestions with a grain of salt, because there is no 100% answer to this problem and frankly, large scale applications which are already completed, DO NOT have a solution, you can't retro fit backwards when you are in production.

So that means problem exists as it is there is no ...

2009-09-25T02:12:37.017-07:00

So that means problem exists as it is there is no one who can provide the right solution...

HTML 1.0? Old school shlong bags!

2009-09-16T00:07:20.984-07:00

HTML 1.0? Old school shlong bags!

lol, nope, you are not missing anything. It broke...

2009-07-29T16:20:55.374-07:00

lol, nope, you are not missing anything. It broke mine as well. I'm gonna live with the errors instead of trying to figure out each and every CSS rule change I'd have to handle.

This fixed my Invalid Viewstate errors but broke m...

2009-06-26T10:20:23.342-07:00

This fixed my Invalid Viewstate errors but broke my css. Am I missing something?

anybody tested for <!DOCTYPE HTML PUBLIC "...

2009-06-08T15:21:04.996-07:00

anybody tested for
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 1.0 Transitional/EN">

instead of
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 ransitional//EN">

the problem solve with HTML 1.0 as well? If i change to HTML 4.0 the styles seem to be mess up so just wondering anybody try with HTML 1.0

There are other reasons also for this as I underst...

2009-06-02T08:46:35.198-07:00

There are other reasons also for this as I understand :
1. That your HTML is not correct.
2. Dynamic server controls which alter the control tree of your aspx page.

Im gonna try this out, and if it works - you are t...

2009-05-17T07:53:00.000-07:00

Im gonna try this out, and if it works - you are the king.
I'm busting my brains for weeks on this problem.

I wasn't really thinking fault. Just solution. Th...

2009-05-07T07:59:00.000-07:00

I wasn't really thinking fault. Just solution. There are many things to get mad at IE about -- how IE renders differently then other browsers for example. However, in the end, I need to find solutions with the things I can change, live with the ones I can't change and know the difference between the two.

Thanks for this post, this problem has been drivin...

2009-05-06T20:31:00.000-07:00

Thanks for this post, this problem has been driving me insane and its great to see a workaround. But I've checked my XHTML against the W3C checker and it says it's compliant. So, it appears to be a bug in IE 7/8. You're implying that it's our fault, not IE. :)

So what is the root of this problem? And why does ...

2009-05-03T20:29:00.000-07:00

So what is the root of this problem? And why does it happen only with IE8? Will there be an update to ASP.NET AJAX to fix this?