I'm experiencing non-responsive menu clicks while running on IIS7 in the "ASP.NET v4.0" Application Pool. Everything works fine in the "ASP.NET v4.0 Classic" Application Pool.
Here's what I experience:
Clicking WebDataMenu items soon causes my app to become unresponsive. Once it "locks up" you can no longer navigate to another page in the app. The wait cursor spins for several seconds, but the app refuses to go to another url. You can't even type a new page name into the address bar -- same results: wait cursor and then nothing. IIS evidently refuses to serve up new pages. The app is effectively dead.
This behavior only occurs after clicking menu items. It does NOT occur when clicking around on other links and buttons. And it only happens in the "ASP.NET v4.0" app pool. Everything works great in the "ASP.NET v4.0 Classic" app pool. It is also random, because you cannot predict which menu item will trigger the issue, and you cannot predict how many menu clicks it will take. But usually about 3 - 10 clicks is all it takes. Then the app becomes unresponsive.
I do not get any first chance exceptions in the debugger. The output window is clean.
I cannot reproduce this in a test app. It evidently only happens in my app, which is loaded with nothing but IG and stock ASP.NET controls.
Have you seen anything like this before?
My aspx code:
<ig:WebDataMenu ID="WebDataMenu1" runat="server" onitemclick="WebDataMenu1_ItemClick" BackColor="Transparent" Font-Names="Verdana" Font-Size="8"> <GroupSettings Orientation="Horizontal" /></ig:WebDataMenu>
Hi raywhite,
The Office Ribbon for asp.net is a good product idea. I have submitted a new product idea for you on your behalf to our product management team. Our product team chooses new product ideas for development based on popular feedback from our customer base. Infragistics continues to monitor application development for all of our products, so as trends appear in requested features, we can plan accordingly.
We value your input, and our philosophy is to enhance our toolset based on customer feedback. If your feature is chosen for development, you will be notified at that time. Your reference number for this product idea is #13010154.
For further help with the behaviors with the WebDataMenu when deployed to IIS 7.0, let me know if I can be of further assistance. It does appear this problem may be isolated to within your project. A network profiler may provide good information to figuring this out. If you send me the network profiler log, I will be happy to analyze this further for you. I will create a private support case for any next steps you wish to take.
Thanks!
I'll probably replace the WebDataMenu with some other third party component. Maybe Telerik. But I really wish IG had an Office Ribbon so I didn't need a menu at all.
Thanks for trying...
There was a service release issued for NetAdvantage 2012 vol 2 mid-January. With this update you will be brought upto assembly build 20122.2054.
I tested with both assembly build (20122.2031) and (20122.2054) and following your steps, I have been unable to reproduce a behavior where clicking on a menu item, the click is unresponsive.
Understanding that you have been unable to get this behavior to reporduce in a test sample, it is possible that this issue is somehow isolated to yor project. The next step you can try for running this down, is to use a network profiler and see what is happening to the request... for instance what information do you get back in the response body.
I hope this helps. Please let me know if I can be of further assistance regarding this matter.
I'm using version 12.2.20122.2031. Is there a newer version?
I was also not able to reproduce this in a test app, so there must be something wrong with my app. But I am certain this only occurs when first clicking a menu item. I tested that many times to be certain of the cause.
My app has ActivateOnHover set to 'true'.
<%@ Register Assembly="Infragistics4.Web.v12.2, Version=12.2.20122.2031, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb" namespace="Infragistics.Web.UI.NavigationControls" tagprefix="ig" %>
I have been unable to so far reproduce this behavior in my test application deployed to IIS7.0. Though at the same time, I want to ensure I'm testing with the same NetAdvantage version and assembly build as you are using. Can you provide me this information?
For the purposes of my test, I used NetAdvantage 2012 volume 2, build '2054'.
My test application has ActivateOnHover set to 'false', and in IIS, I tested were my Application Pool is .NET Framework 4.0 and Managed Pipeline Mode is set to Integrated (also tested Classic).
Please let me know the above info and I will test this issue further.