We have been using Infragistics 2006v1 for a few years without any issues. We recently renewed and updated our site to Infragistics 2009v2. After a day or so of uptime on our production server we start getting random exceptions with the infragistics controls. The exact exception that start it off is below. The only way to fix this is to do an IIS reset and then it will be stable for a day or so.
** Exception : Object reference not set to an instance of an object.
** Stack Trace : at
Infragistics.WebUI.Shared.GlobalCssHelper.GetPageContainer(Page page, Boolean create)
control, Page page)
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Thank you for a report.That issue was introduced around 7-8 months ago due to work around memory leaks on server which occurred in some specific applications. Around 2 months ago, that was reviewed and current version uses different logic. Particularly the GlobalCssHelper class which was used in earlier versions before AppStyling, was deprecated and removed from logic.
Please get latest service release, it should not have that issue.
I checked source codes and found that that fix did not go to the RELEASE build yet. I hope, that will be available in coming service releases.
Thank you for your help. Is this true for both 2009v1 and 2009v2?
Actually currently source codes for RELEASE of 9.1 and 8.3 contains fixed version. Codes were merged with DEV on 10/26/2009 and version 9.1.20091.2113 was built on 10/27/2009. I expect that public dlls for 9.1/8.3 already contain that.
The version I have in my infragistics download are2009v1.1001 NetAdvantage for Web Client 2009 Vol. 12009v1.2101 NetAdvantage for Web Client 2009 Vol. 1 - ASP.NET Service Release
Does 2101 have the fix or just 2113
This is a really big help. thank you.
I am experiencing the same issue with 2009.2. I was also experiencing the same issue with 2009.1, and was praying that the 2009.2 version would contain this fix.
Is there any time table for the first service release?
Same here. We really need a fix for this. Please help!
I have submitted a corresponding support request to emphasize the urgency of this problem. I can't deploy my application with unpredicatable stability and requiring frequent IIS resets.