We installed .NET 4.5 on a server with .NET 4.0 Asp.Net web applications. New .NET 4.5 applications work ok, but existing 4.0 webform applications have a problem: http post request with WebForm_DoPostBackWithOptions don't work anymore. If the requests are
traced with Fiddler, Fiddler reports that the request body is empty. Something is going wrong. The weird thing is that the problem only occurs when using IE, and not with Chrome or FireFox. Any ideas? Upgrading the 4.0 applications to 4.5 doesn't help either.
I am from .NET Framework Compatibility team. We would like to understand this better. Could you contact us on netfx45compat at microsoft dot com with small repro of your project that we can try in-house?
bj_lappensch...
0 Points
2 Posts
Problems with WebForm_DoPostBackWithOptions after installing .NET4.5
Jan 09, 2013 06:35 PM|LINK
We installed .NET 4.5 on a server with .NET 4.0 Asp.Net web applications. New .NET 4.5 applications work ok, but existing 4.0 webform applications have a problem: http post request with WebForm_DoPostBackWithOptions don't work anymore. If the requests are traced with Fiddler, Fiddler reports that the request body is empty. Something is going wrong. The weird thing is that the problem only occurs when using IE, and not with Chrome or FireFox. Any ideas? Upgrading the 4.0 applications to 4.5 doesn't help either.
Thanks,
Bert-Jan
radamanthys
Member
228 Points
74 Posts
Re: Problems with WebForm_DoPostBackWithOptions after installing .NET4.5
Jan 10, 2013 09:03 PM|LINK
Ate you running your sites on IIS?
bj_lappensch...
0 Points
2 Posts
Re: Problems with WebForm_DoPostBackWithOptions after installing .NET4.5
Jan 16, 2013 06:08 PM|LINK
Yes, sites run on IIS 7.5
VarunGupta
Member
6 Points
3 Posts
Re: Problems with WebForm_DoPostBackWithOptions after installing .NET4.5
Apr 15, 2013 12:12 AM|LINK
Hello Bert-Jan,
I am from .NET Framework Compatibility team. We would like to understand this better. Could you contact us on netfx45compat at microsoft dot com with small repro of your project that we can try in-house?
Thanks
Varun Gupta (Microsoft .NET Framework Compatibility Team)