Dropdown AutoPostBack not working with IE10 for Win 7 - asp.net

I just download IE10 for Windows 7 64bit [it is released today] and immediately found that my site's Dropdown AutoPost Back is not functioning. I am not getting any Error, but couple of warning in IE10's development Console. All of them are generated on ASP.NET Ajax toolkit elements.
I want to post it as bug to IE 10 team, but I found that my development server doesn't have this problem, only production server has this problem. Not mention the CODE IS EXACT same on both server. However development server is on Azure VM with Windows 2012 and production server is shared web hosting with Windows 2008 [edition not known]
Does this make any difference on browser ?
EDIT: if it matters DO NOT TRACKER is off ...
EDIT2: I found that problem is only on IIS 7 based shared hosting, on Windows 2012 the site works just fine. SO probably IIS 7 doesn't know IE 10 and hence it doesn't render it properly.

Scott Hanselman explains this on his blog.
http://www.hanselman.com/blog/BugAndFixASPNETFailsToDetectIE10CausingDoPostBackIsUndefinedJavaScriptErrorOrMaintainFF5ScrollbarPosition.aspx

Related

Site compatibility issue with default IE11 comes with Windows 10 - Hosted on Azure VM

We have a Dotnetnuke site hosted on Azure VM.
Azure VM details
Server : Windows Server 2012 R2
IIS: - 8
.Net Version – 4.6
Our Site(http://dev2-cms-molpower.eastus.cloudapp.azure.com/Admin/MOLPowerCMSLogin) is compatible with all standard browsers except IE11 that comes as default with Windows 10.
IE11 with Windows7 and Windows 8 are also working fine.
Problem we noticed with IE11/Windows 10 are :-
Error “ '__doPostBack' is undefined”
Error: 'WebForm_DoPostBackWithOptions' is undefined
Don’t render script tag for webresource.axd
Don’t render hidden field “__EVENTTARGET” and “__EVENTARGUMENT”
After googling I under stand , IIS doesn't recognize user agent header sent by IE11.
Workaround I noticed , either apply latest server patch or update .Browser file .
I tried with updating .browser file in IIS for my site but it didn’t help me.
Not sure about which patch to apply

IIS 8 localhost page not loading on Windows Server 2012

I am currently trying to open a webapp from IIS 8 on a VM using Windows Server 2012, I was previously getting error pages and I think I have fixed all those problems. Now when I click browse it opens chrome and says loading but the page never loads.
I ran the exact same project though IIS 8 on Windows 8 and it worked perfectly. The project was originally created using Visual Studios 2012 and it ran perfectly from there too, on Window 8. I have tried everything I can think of.
Does anyone have any suggestions?? Thanks

Visual Studio 2010 with IE 11 and 2.0 classic web pools

i am using IIS in a visual studio 2010 solution with Integrated 4.0 and 2.0 Classic web pools. when i use IE 11 over the Inet to "try" and login, the app fails.
yes i know about changing settings but this cannot happen on my web site. Any thoughts on what is happening and / or why?
i have not tried to bring up the app using IE 11, any ideas on the "surprises" i will find? thanks for any comments, they are appreciated.
I had the same issue using VS2010. I knew this problem existed with IE 10 and I somehow let the automatic updates install IE 11.
I found this fix from MS and it resolved the issue for me:
http://blogs.msdn.com/b/visualstudioalm/archive/2013/09/17/coded-ui-mtm-issues-on-internet-explorer-with-kb2870699.aspx
My apologies if this is wide of the OP's question, but I also had problems using Studio 2010 with the new IE 11 (googling those two terms led me here, and John B's post led me to answer). Specifically Studio's debugger would fail to attach to IE 11 while I was launching a Silverlight project.
John B linked to an MSDN patch. After I installed it, Studio still would fail to attach to IE11, but at least this time I got an error message: "The 32-bit version of the Visual Studio Remote Debugging Monitor (MSVSMON.EXE) cannot be used to debug 64-bit processes or 64-bit dumps. Please use the 64-bit version instead."
From that message I found out that Silverlight can only run in 32-bit mode. And both IE10 and IE11 cannot run in 32-bit mode when they place all the tabs into a single 64-bit process. However, if "Enhanced Protected Mode" is enabled (which it was for me by default, it's under Internet Options' Security tab) and you change this registry value...
HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main\TabProcGrowth
...to be something more than 0 (I set mine to 5, not sure it matters much as long as it's more than 0), then IE11 is able to spawn 32-bit processes and Studio is able to launch a 32-bit browser instance that it can attach the Silverlight debugger to.
A few related articles...
http://support.microsoft.com/kb/2716529
https://superuser.com/questions/561036/unable-to-open-ie-10-in-32-bit-mode
http://connect.microsoft.com/VisualStudio/feedback/details/774460/cannot-debug-silverlight-win7-x64-ie10
Hope this helps someone.

Crystal Report v10.5 toolbar not visible on Firefox but visible on IE and Chrome

I am using crystal report v10.5 with visual studio 2008 to develop crystal reports.The problem I am facing is with the toolbar which is not visible on Firefox but it is visible on IE and Chrome.
I have installed same version on both development machine and on production server which is Crystal report v10.5. My development machine is Windows 7 32bit and production is Windows 2008 64bit.
I have tried solutions mentioned on numerous forums such as
Copy the 'aspnet_client' folder from 'C:\Inetpub\wwwroot' to 'C:\Inetpub\wwwroot\your-website-name'.
create a new virtual directory in your web site and point it to "C:/Inetpub/wwwroot/aspnet_client".
Application pool is to be changed to "Classic" instead of "Integrated".
Set the application pool of your application to operate under LOCAL SERVICE permission.
But still I am not able to show toolbar on Firefox.
Configurations:
Visual Studio 2008
.Net Framework 3.5
Crystal Report for runtime 10.5
Windows Server 2008 64bit
Can anyone point me to the right direction?
Edit- I recently upgraded from Windows 2003 to Windows 2008 and the same version for CR 10.5 was working as expected without any mentioned solutions above.
Thank you
You need to add ClientTarget="uplevel" to the page directive of the aspx file.
<%# Page ClientTarget="uplevel" ... %>
It seems that there are compatibility issues between CR and certain browsers depending on the version of CR. There is a very helpful post here that has links to a compatibility table. I suggest to check that out and then see if you can maybe upgrade to a different version of CR.
Hope that helps.
My application use last Crystal Runtime on x64 server and work on firefox too.
1) If the toolbar is not visible there should be a reason (press F12 in firefox.. what do you see? 404 error? 500 error? Please post it!)
2) Crystal Reports Runtime 13.x IS available for X64 servers too.. There is no reason to use an old runtime containing many bugs resolved in other releases.
You can get it here (get MSI 64 bit - Support Pack 8)
After updating runtime you have to copy the 'aspnet_client' folder again fi you did (new virtual directory in your web site is a better approach)
After updating runtime you could need a little hack to let an application developed with older dll work with new dll. There are few rows you have to put into web.config described here.

ASP.NET 4 application issue on iis 6 on windows xp 64bit

I have deployed an ASP.NET 4 application to IIS 6 on Windows XP 64bit. This application is working perfectly from an IE8 session launched from Visual Studio 2010 and Cassini from the same XP workstation.
However once I deploy it to IIS 6, on the same box, and open it from IE8 directly, I get all sorts of issues with control widths and layout and also some jQuery errors for my datatable control.
Now here's the really weird part if I open the same IIS 6 web site from firefox using the exact same url everything works fine.
Why would this be happening?
So you have to add a custom header and make sure that you are forcing the ie mode to be 8.
X-UA-Compatible:IE=8

Resources