We are using an app which is designed in MVC and Silverlight. That app is working fine in IE10. But we are not able to run the app in IE11. We have set of javascript functions with is used to do validation on our app. Those functions are not at all working. I am getting 'undefined' error. Even i have tried with <meta http-equiv="x-ua-compatible" content="IE=10"> also. If any one can help me, you are my Savior.
Thanks in Advance.
Also note some detection fixes: 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
Add localhost to compatibility setting in IE 11.
If you're doing browser detection or x-ua-compatible, you should not be. There is no guarantee that either of these methods will work in the future.
.NET Browser Definitions will not detect IE11 as Internet Explorer, resulting in the "...undefined" errors.
You should instead use feature detection to determine features supported by the browser.
In a pinch, the only official method (per the IE11 Compatibility Changes guide on Microsoft's site) for detecting IE11 is to check for the "Trident" token in the User Agent.
I had tried all the hotfixes which described the issue. "Script Error encountered", "'__doPostBack' is undefined" but only solution that worked for me was .NET 4.5 . You can read more about my findings in these questions CrossPostback ,AJAX Controls and ASP.NET generated postbacks work for .NET 4.5 , not .NET 4.0 in IE 11 and WebResource.axd not working with Internet Explorer 11
Related
I have a question about applications developed with older versions of Asp.net like Asp.Net 1.1 for example.
I would like to know if an application developed with an old version of Asp.Net like Asp.Net 1.1 can run properly on new browsers such as Microsoft Edge, Chrome, chromium ... etc?.
Are there any compatibility issues for example?
thank you for the answer
This is a very hard question to Google because there are different versions of ASP.NET out there. What I want to know is the versions of Windows Server that support ASP.NET 2.0 (no MVC, no CORE) just the original version that was released back in 2006 (See: https://en.wikipedia.org/wiki/.NET_Framework_version_history#.NET_Framework_2.0)
Thanks!
First, only Windows Server 2012 and above are supported now.
Second, you have to manually enable ASP.NET 3.5 there, which supports ASP.NET 2.0 web apps,
https://learn.microsoft.com/en-us/iis/get-started/whats-new-in-iis-8/iis-80-using-aspnet-35-and-aspnet-45
However, keep in mind that such ASP.NET 2.0 apps are ancient. Upgrade if you can.
We are planning to upgrade the browser to IE 11. So was testing all the web application whether it is compatible with IE 11.
One Asp.net 4.0 project uses Infragisitcs 12.2 and the WebDatePicker doesn't display the Date in IE 11 after hosting to IIS server 7.5. It was working fine in IE 10.
It was working fine in my local machine with IE 11. But just when it is hosted in IIS 7.5 it is not working.
Is it something related to the IIS setting.
Can some one please help on this.
As stated at http://www.infragistics.com/support/supported-environments IE11 is supported when running Infragistics products 13.1 and later. It means IE11 has not been tested with older version of IG product.
We have recently taken on support of a web application that was written many years ago and targeted v1.1 of the .net framework. It runs on Windows Server 2003/IIS 6 environment.
After looking at the configuration of the site in IIS the target framework is set to 2.0.
Given that extended support for .net 1.1 will cease in October of this year (http://support.microsoft.com/lifecycle/?p1=1249) I am trying to ascertain whether the site will still use any of the .net 1.1 framework assemblies given that the application is built and compiled in Visual Studio 2003.
I am assuming this is the case because although ASP.net 2 is set as the target framework
in IIS (and therefore the aspet_isapi.dll invoked is the .net 2 one etc) the assembly is a .net 1.1 assembly and will therefore still use the 1.1 framework. However, is this assumption actually true?
The website only has another year or so to live before being replaced by a new solution entirely so I would prefer not to upgrade it if possible and run the risks such changes bring with them.
However, we obviously can't run something on an unsupported version of the framework if any element of if that framework is actually being used.
Any thoughts would be appreciated.
Update:
It would seem that .net 1.1 is a core component of WS2k3 so you can't just uninstall it. I could have attempted to remove the ASP.net component but I don't think that would fully uninstall everything and given that the dev environment is shared I can't risk causing any issues right now.
However I have previously set everything up on my local machine (Windows 7/IIS 7), so I changed the application pool to point at .net 2 (it was already running in classic pipeline mode), uninstalled .net frameworks 1 and 1.1 and cleaned up the files left behind afterwards.
The result was that the site ran absolutely fine, which would suggest in an IIS 7 environment at least that I don't need to worry about upgrading given we are running under .net 2 within IIS.
It's not an ideal test as it isn't a mimick of our live environment. I'm going to post a question on MSDN and asp.net to see if any Microsoft folks can add anything more definitive. I will post back here with any updates.
Just because official support will end doesn't mean Microsoft will pull the plug and force an uninstall of .NET 1.1 via Windows Update. It only means that:
if a gaping hole in the framework's security is ever found, they'll not fix it;
There won't be redistributables for the next versions of Windows, and the next version of IIS won't run it.
So the application will still run in a year. If you leave the server alone, the application might run until the machine breaks of old age.
So my suggestion is relax, and focus more on the new solution.
I got the answer to this questions after reading this link (provided as an answer to this question on the ASP.net forums)
http://msdn.microsoft.com/en-us/library/ms994381.aspx
Under "Application Load Mechanisms and Possible Issues" it states:
By default, an application built using the .NET Framework will run using the version of the Framework it was built against if that version is installed on the computer
It then goes on to detail (for .net 1.1 and 2.0 at least) when a particular version of the framework is used.
Essentially, because our server has both 1.1 and 2.0 installed the application will still be using version 1.1. If 1.1 was not installed then it would run by default under 2.0, which explains why the web application still worked after I uninstalled .net 1.0 and 1.1 from my local machine.
Given that the live server is W2K3 and I can't remove .net 1.1, I will be rebuilding my application to target .net 4.0.
I'm having a little trouble with my panning functionality in my Dev environment. The way I implemented panning functionality adding JQuery to drag an image behind a panel control. The panning functionality is available after zooming into the image. So I zoom into the image with zoomin/zoomout functionality, then I pan or drag the image behind the panel control. This works great in my local environment and even when I deploy the website to my local IIS. However, when I deploy to the Dev server, the image does not stay behind the panel control or is not contained within it. Are there any suggestions on what might be causing this? Below is some information on approaches I've tried.
I did a comparison on the two environments.
Configuration on my local environment:
.NET Compact Framework 2.0 SP2 (Version 2.0.7045)
.NET Compact Framework 3.5 (Version 3.5.7283)
.NET Framework 4 Client Profile (Version 4.0.30319)
.NET Framework 4 Extended
.NET Framework 4 Multi-Targeting Pack
AJAXControlToolkit: Version 3.5.50508.0
Configuration on Dev Server:
.NET 2.0: .NET 2.0 SP2 (Version 2.2.30729)
.NET 3.0: .NET 3.0 SP2 (Version 3.2.30729)
.NET 3.5: .NET 3.5 SP1 (Version 3.5.30729.1)
AJAXControlToolkit: Version 1.0.20229.0
Could it be that the slight mismatch in versions is causing the problem? I was thinking of somehow matching the .NET versions on my local machine to that of the dev server. Would this cause an issue? Also I am using Visual Studio 2008 Team System SP1 for development.
I tried adding the AJAXControlToolkit.dll file to the Dev server, but I get the same results.
I tried setting the panel control to style="overflow:hidden", but that didn't seem to work either.
Here is the piece of code I think is causing the problem:
<div id="draggable" style="position:relative;" onmousedown="makeDraggable(); return false;">
<img id="myimage" src="[path to image]" usemap="#circles" onmouseover="changeToHand()" />
</div>
</asp:Panel>
Any help is greatly appreciated!
The issue was isolated to IE. Mozilla and Chrome were fine. So I went to the configuration on IE and realized compatibility view settings were on. If you are on an intranet, make sure the compatibility view settings are off for that too.