Hey guys,
(I had posted a comment similar to this at http://es.infragistics.com/community/forums/p/13817/379249.aspx#379249 but that thread is > 4 years old, and I haven't heard anything in > 2 weeks, so I'm thinking that the thread is dead. If I get a resolution here, I'll update the post there as well.)
I am having a problem whereby clicking on a WebDateChooser's button does not bring up the calendar. (Typing in a date still works.) This problem occurs on some machines and not others.
I am using Infragistics 20111.2238 (which is the current hot fix version, as of 2012-10-29. We have also experienced this problem under 20111.2178, and under 20101.*), and the problem shows up on certain computers and not others. It is a consistent problem in that for a machine that does not work, it ALWAYS does not work. It started off as just a single machine that was failing, and over the past year, has increased to over 10 machines. (This represents about 10% of the user base... The rest do not experience this problem...) When a user tries to click on a WebDateChooser, they get a javascript error:
Webpage error details User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; WOW64; Trident/4.0; SLCC1; .NET CLR 2.0.50727; InfoPath.2; .NET CLR 3.0.30729; .NET CLR 3.5.30729; OfficeLiveConnector.1.5; OfficeLivePatch.1.3) Timestamp: Tue, 23 Oct 2012 15:26:20 UTC Message: Unspecified error. Line: 347 Char: 40 Code: 0 URI: http://lis.natureconservancy.intranet/Lis/ScriptResource.axd?d=VuwY2H3er3wYe4Qah1czdsslKfF83yH1K7xOe8TfGbnA2a_NNiV-C4Nq1oqlQx-h2Ytnw7DbNLIKXVbrUo2SpTQpySA4H1aTMgHW8gd_FtZc4_cDgSBZj2OqOXNCTd8ds6M9RpmJPlzTKWrXE1GzxlZYG2_kpru-dfK-D2-1ETcpLxjabE6R1ilKZJzvT_XdgphSAQ2&t=ffffffff92365c45
We have downloaded the ScriptResource file in question, and line 347 takes us to the while statement. Character 40 is the "i" of the "if" keyword.
while(o<0&&(pe=pe.parentnode)!=null)if(pe.filters)o=100;
This .axd file maps to the ig_webdropdown.js file. (Line #354 in the developer copy of the .js file, which contains some comments, whereas the .axd does not.)
Notes on our debugging process:
- We have examples of this working and broken in identical versions of IE8 from a client's machine directly (= Not Citrix. See Below.)
- We have examples of this working and broken in identical versions of IE9 from a client's machine directly (= Not Citrix. See Below.)
- We have examples of this working and broken when using the exact same instance of IE running over Citrix. (To me, this is the most convincing argument that it's not a browser-specific problem.) The Citrix environment is a single server, NOT a farm, and when accessing the website via Citrix, some machines always fail, and some machines always succeed. However, with this problem starting to become more prevalent over the past year, there has to be SOMETHING that is making it start to break. Windows Updates, perhaps? We have compared Citrix Client versions, Java versions (as the Citrix Client runs over Java), and IE versions on the client's machines (even though IE on the client machine "shouldn't" have anything to do with the Citrix copy of IE that's actually running.)
- Compatibility mode is not an issue, because we've tested a "broken" machine with compatibility mode on and off (and with IE8 and IE9). It breaks under all circumstances.
- From a failing computer, it appears to fail no matter who is logged onto the computer. (We use Windows Authentication.)
- From a working computer, it appears to work no matter who is logged onto the computer. (We use Windows Authentication.)
Obviously, the ASP.NET Classic Controls are 2 toolsets behind the times, but I don't have the budget from the client to upgrade to either the Aikido framework or the IgniteUI framework.
I realize that asking for a proper fix might be pushing my luck, but I'm willing to update and deploy my own copy of ig_webdropdown.js if you can help me figure out how to deploy it. In fact, I already tried to split that single line (consisting of a while, an if, and a statement to run) into multiple lines, to make sure that the problem really DOES lie with the IF statement, but I can't seem to get the website to use my copy of the .js file. I have tried following the instructions at:
http://help.infragistics.com/Help/NetAdvantage/ASPNET/2011.1/CLR4.0/html/Web_Deploying_a_Web_Application_that_Uses_NetAdvantage_for_ASP_NET_Controls.html
Namely, I have created a directory for "C:\Inetpub\wwwroot\aspnet_client\Infragistics\20111CLR\Scripts", placed a custom copy of ig_webdropdown.js in it (I added an alert at the top of the file, and one at the beginning of the igdrp_expandEffects(owner,props) function, neither of which are firing), and created a virtual directory called "ig_common" that points to "C:\Inetpub\wwwroot\aspnet_client\Infragistics".
(Note: I realize the instructions are for CLR4.0, and I'm targeting 3.5, but a quick hack of the link didn't take me to equivalent 3.5, 3.0, or 2.0 copies of the file...)
I have also cleared the browser's cache, and upon requesting the .js file directly from IE, am able to download my updated copy of the file.
Thanks for taking the time to read this, and let me know what other information I can provide to help! As I said, I'm willing to roll with a proper fix (new dll's) or just updating and deploying a customized version of the .js file.
Jamie Foster
Hello subhash,
This issue is addressed in a separate support case.
If you have any questions, please let me know as well.
Thank you for the update and additional information.
Attached is a sample using .NetAdvantage 2010 volume 3. Please let me know if it demonstrates the behvaior you are looking for, or if the issue persists.
Hello Vivian,
We are using IE-8.0 browser in both windows XP and windows -7 operating system. Please suggest me the solution as earliest as possible because client would not be able to use my application on windows-7 after migration from XP which is scheduled in very near future.
Thanks
subhash
Hello Subash,
Thank you for the update.
Yes. On the other hand, current browsers are supported in much later versions of .NetAdvantage. For example, IE9 is supported at the earliest in .NetAdvantage 2010 volume 2.
On this note, please let me know the browsers you are using in both Operating Systems. This way we may be able to isolate the cause of the behavior, and may provide an appropriate solution for your application.
For more information on our supported environments for our ASP.NET Classic Controls, please refer to the following documentation: http://es.infragistics.com/help/supported-environments/
Thanks for your quick response.
We are still in .Net 2.0 framwork. My question is that would latest version of infragistics "NetAdvantage 2009 volume 2 with the latest Service Release" compatible with .Net framework 2.0 ?
Subhash