16

I have an ASP.net 4.0 application running on Windows Server 2003.

I am running Windows 8.1 preview with IE 11 and I am getting the

__dopostback undefined error.

I have already tried all of the suggested hotfixes, kbs, and nuget packages and none of them work. I can add the site to the compatibility view settings and everything works fine. I googled but I cannot find any updated browser definition files for IE 11. Has anyone seen updated files or know what I can do to solve the problem.

Like I have said I have already tried everything from this Scott Hanselman's blog article. So please do not post that as a response.

Ian Boyd
  • 246,734
  • 253
  • 869
  • 1,219
Stryder
  • 795
  • 2
  • 9
  • 20
  • I noticed your casing of `__doPostBack` is incorrect in your question, did you type it correctly in the code? (I've done that mistake several times ^^) – Christoffer Mansfield Jul 16 '13 at 10:09
  • 6
    [IE 11 pretends it isn't Internet Explorer](http://www.nczonline.net/blog/2013/07/02/internet-explorer-11-dont-call-me-ie/), so unfortunately, the updated browser definitions that are forward compatible for browsers that call themselves IE 11 don't work. –  Jul 16 '13 at 10:29
  • 1
    @Christoffer it was 4am and you are correct I miss typed in my question but yes it is correct in my code, mostly because it is auto-generated. – Stryder Jul 16 '13 at 20:02
  • @hvd thanks for the link to the article it explains a lot of the behavior I am seeing. – Stryder Jul 16 '13 at 20:05
  • It isn't so much that IE11 pretends it isn't IE as it is IE11 becoming infinitely more standards-compliant. Perhaps, one day, we'll be completely free of the scourge of browser detection. – EKW Jul 25 '13 at 23:26
  • Do you have a possibility to upgrade your project to .NET 4.5 and test to see if it makes the difference? – Yuriy Galanter Aug 19 '13 at 13:37
  • Perhaps one day we'll be completely free of the scourge of Internet Explorer.. – sh1rts Nov 27 '13 at 23:32

3 Answers3

13

I think this is fixed by this KB http://support.microsoft.com/kb/2836939/en-us

More details (for older OS's and .NET versions)

KBs for the IE11 GDR:

  • 2836939 .NET 4 - Win7SP1/Win2K3SP2/Win2K8R2SP1/Win2K8SP2/VistaSP2/WinXPSP3
  • 2836940 .NET 3.5 SP1 - Win2K3SP2/Win2K8SP2/VistaSP2/WinXPSP3
  • 2836941 .NET 2.0 SP2 - Win2K3SP2/WinXPSP3
  • 2836942 .NET 3.5 SP1 - Win7SP1/Win2K8R2SP1
  • 2836943 .NET 2.0 SP2 - Win7SP1/Win2K8R2SP1
  • 2836945 .NET 2.0 SP2 - Win2K8SP2/VistaSP2
  • 2836946 .NET 2.0 SP2 - Win8RTM/WinRTRTM/Win2K12RTM
  • 2836947 .NET 3.5 SP1 - Win8RTM/WinRTRTM/Win2K12RTM
Scott Hanselman
  • 17,712
  • 6
  • 74
  • 89
  • 3
    **It's important to mention** : I also installed it and nothing worked. - until I renamed `app_browsers` to another name( or delete) - then - everything worked. – Royi Namir Dec 12 '13 at 14:58
6

I tried every patch that I've seen listed on the internet, including the ones listed here. The only thing that actually seemed to work was installing the .NET 4.5 Framework on the server.

Get it here: http://www.microsoft.com/en-us/download/details.aspx?id=30653

Hope this saves someone a few of the hours I've lost on this one.

ckozl
  • 6,751
  • 3
  • 33
  • 50
2

We are currently using asp.net 4.0 and had this issue for a while. It first appeared with IPad users, and we solved it by creating a IPad.browser file. Then this bug appeared for IE11 users. We installed the KBs above with no luck. The solution: delete all *.browser files (and even the App_Browsers folder itself). Now it works!

Patrick
  • 21
  • 1
  • You are right. I also installed it and nothing worked. - until I rename app_browsers to another name( or delete) – Royi Namir Dec 12 '13 at 14:57