Good day,
This issue occurs using both v13.2 and v14.1 (rev 2011) of the Infragistics ASP.NET controls.
We are having issues with the webschedule mini-site when we are hosting it in IIS 7.5 using IE 11.
The date and time fields are not populated when the control is loaded (Date shows NULL, and time is blank), which causes errors. The error being returned is that a property cannot be found for a specific control (in this case, the "UltraWebToolbar2" control located on "AddAppointment.aspx", the "Items" property cannot be found in the control, see attached screenshot). When using older browsers such as IE 10, it works fine though. Curiously, using IIS 6 and IE 11 also works fine.
I've noticed that when setting the website in compatibility mode in IE the webschedule works fine, but this is a problem as the entire site CAN NOT run in compatibility mode, and the users aren't savvy enough to switch between the two modes as required.
I've tried setting the META tag "X-UA-Compatible" on the "AddAppoinment.aspx" page to everything from IE=6 to IE=10, and the IE=EmulateIE7 trick too, no luck. I've also tried setting a custom header in IIS to the above values, but no success.
Also, the default webschedule mini-sites provided by your installation program has issues. The version numbers in the ASPX pages and Web.config files are incorrect (this happened in both the v13.2 and v14.1 releases). I had to manually change the assembly numbers to the correct assemblies in the ASPX/web.config files. If this is incorrect, please provide the assemblies required so I can deploy the mini-site correctly.
Please assist with urgency, this part of the program is used by our clients on a daily basis and they are rolling out IE 11 to all machines in their infrastructure.
Thank you,
Good day Troy,
After much research and troubleshooting, I've finally found a combination that seems to work to resolve my problem.
First, I added the "X-UA-Compatible" meta tag to the "AppointmentAdd.aspx" page and set it to "IE=EmulateIE7".
Lastly, I changed the "AppointmentAdd.aspx.cs" page and added a "Page_PreInit" event. In it, I have this simple line of code:
"Page.ClientTarget = "uplevel"; "
This tells the browser to use the rendering capabilities of IE 6, which is fine for this specific problem.
These two changes made the "AppointmentAdd.aspx" work perfectly in IE 11, as well as the lower version IE browsers.
I found this article leading me to the correct path: http://jwcooney.com/2013/11/27/detecting-and-upleveling-asp-net-pages-for-ie11/
Can you maybe have the development team include this change in all future releases, please? Or at least upgrade the webschedule to the newest controls (it
is still using the UltraWebToolbar !).
Also, please have the dev/deployment team look into correcting the version numbers in the ASPX and web.config files for each release.
Hope this helps anyone else having this problem!!!
Regards,
Eduard Kruger.
Hi Eduard,
I am continuing to follow this post. Let me know if you need additional assistance.
The first step to determine what may be happening here is for us to reproduce the issue in a small sample deployed to IIS7.5 when browsing with IE11.
To this end I have pulled together a draft of a test sample. I will ask that you modify this sample to reflect your scenario as closely as possible such that it reproduces the issue you are reporting here. Or, if you prefer, you can create your own small sample. Mainly I just need a sample that I can build and run that I can deploy here that reproduces this issue. Please then attached the test sample to this forum thread. I will then further research this matter for you.
As a note, the sample I have here utilizes the WebSchedule sql server database. You can find the scripts for this sample database on your machine at : C:\Users\Public\Documents\Infragistics\2014.1\ASP.NET\WebSchedule\Data (http://es.infragistics.com/help/aspnet/webschedule_deploying_to_microsoft_sql_server.html)
For the second issue that pertains to the version numbers in the aspx/web.config file, I propose to create a new (separate) forum post for support on that issue. This is so we can address 'that' issue separately and specifically, allowing this post to be specific to addressing the hosting in IIS and IE11 issue.