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)
at Infragistics.WebUI.Shared.GlobalCssHelper.OnInit(WebControl
control, Page page)
at Infragistics.WebUI.WebDataInput.WebTextEdit.OnPreRender(EventArgs
e)
at System.Web.UI.Control.PreRenderRecursiveInternal()
at System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Hi Chris,
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.
Hi Gary,
2 files in shared dll were modified: RenderBase.cs and ClientScript.cs.
It is better to get latest service release. Though, If you prefer to have those files, then please give me your email, so, I can send those files.
Thanks Viktor
We have the latest release we just need to install it. I was asked to verify the fix for our client. I think your first answer plus this is fine.
Thanks
Gary
Hey Viktor,
Does the release of 2010 Vol1 contain the fix as well?
Thanks,
Jamie
Hi Jamie,
Yes. Fixes are applied for all (old and new) versions.
Hi Viktor ,
Is this issue been taken care of in NetAdvantage for Web Client 2009 Vol. 2 - ASP.NET Service Release (20092.2099).
Yes