With the release of IE 8 I have been experiancing issues with the UltraWebMenu 6.1 running under .NET 1.1
The first issue was that access was denied to HM_Arrays.js (I dont get this error in versions of IE prior to 8, nor did I get it in the IE 8 Beta releases).
The Second error is that the UltraWebMenu does not show up at all (shows up in IE < 7 and was showing in beta versions of IE8) in IE 8 release.
I could only get the second error to occur after I managed to clear the first error by grating ASPNET and IIS_WPG full control of the website.
Just a further tidbit. We had issues using Response.Browser.JavaScript. Apperntly this will always return false for IE 8 release (we had to comment out code that was using it). I belive this is related to Microsoft not supporting the .NET 1.1 framework and as such did not update the framework code that tells Response.Browser.JavaScript that IE 8 is a supported browser that has javascript. Which means that the UltraWebMenu could be using this same code, determining that IE 8 doesnt support javascript and hiding itself.
The maintenance period of NetAdvantage for .NET 2006 Volume 1 ended prior to the release of Internet Explorer 8. This means that no further code changes are being made to this version, such as to introduce compatibility with Internet Explorer 8.
We're working toward compatibility with Internet Explorer 8 in our upcoming release of NetAdvantage for Web Client 2009.1. We won't have all of the regression testing completed as we'd like, since the browser was only released-to-market very recently.
Due to the magnitude of the required changes, earlier verisons of the toolset are not likely to be updated for Internet Explorer 8 compatibility.
Yes and No, in 2008.3 (which we have a license for) there is no .NET 1.1 version (on top of that I'm sure it would have the same issue due to the framework on which it is built). We are currently in the process of updating our product to .NET 3.5 and are close to the end of the project.
The problem is that we are trying to find a workaround so that our existing customers that download IE 8 can survive this transition. I am fully aware that 6.1 is not supported, all things have an end in the development cycle... well unless Microsoft is concerned (which it is). More of what I'm looking for is a hack, cheat, trick, or any other dirty method that might put off the inevitable. I'd really like to avoid the term "Royally Boned" when talking to our customers.
Thats more the intention of my post, rather than asking for a fix I'm just need some insight to the code, if there is ANY kind of method that I can use to de-break this for a couple more months.