Our company just installed an IE 11 patch and it broke the CuteEditor that we are using for an internal ASP.NET 3.5 website. We have changed the X-UA-Compatible to IE11 and EDGE with no success. It works fine on our local machines, but does not work on the server. Our enterprise has Enterprise Mode and Compatibility mode setup for Intranet sites. After the patch installed, we no longer have the CuteEditor toolbar and the textboxes are readonly. It works fine in Chrome, but that's not really a viable solution for a large enterprise right now.
Here is a link to the MS for the patch that was installed
Can anyone shed any light on what we need to do?
We found a fix for the issue. We had to disable partial rendering in the update panels that the cuteeditor controls were in.
Related
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.
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.
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
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.
I have a strange question!
I have developed a website in asp.net webforms, I've tested this website in IE7, IE8, Ie9 (RC), Firefox, Chrome and Safari, in Windows XP and Windows 7. Everything works fine.
But in Internet Explorer in Windows Vista, does not working. The website opens in browser, but when the application needs a postback it does not work. I don't know why it is happening. If someone could suggest something to accomplish this? I appretiate!
Thank you!
Att,
Highly doubt it's the OS... Check your internet options...
A failed postback could be due to a javascript error. Have you tried using the Javascript console (Shift+F12) in IE8, or using Firebug Lite in versions lower than IE8? Could you turn off surpressing javascript error notifications to see if this presents the issue?