The version i am using is Infragistics2.Win.Misc.v7.2 (Version 7.2.20072.61)
We aren't quite sure how are users are getting this. They say it happens randomly. Can anyone shed some light on the problem?
System.InvalidProgramException: Common Language Runtime detected an invalid program.
at Infragistics.Win.FormattedLinkLabel.FormattedTextEditorOwnerInfoBase.GetValue(Object ownerContext)
at Infragistics.Win.FormattedLinkLabel.LinkEditorInfo.SyncOwnerInfo(Boolean forceRegetValueFromOwner)
at Infragistics.Win.FormattedLinkLabel.FormattedLinkEmbeddableUIElement.SyncOwnerInfo(Boolean forceRegetValueFromOwner)
at Infragistics.Win.FormattedLinkLabel.FormattedLinkEmbeddableUIElement.PositionChildElements()
at Infragistics.Win.UIElement.VerifyChildElements(ControlUIElementBase controlElement, Boolean recursive)
at Infragistics.Win.FormattedLinkLabel.FormattedLinkEmbeddableUIElement.VerifyChildElements(ControlUIElementBase controlElement, Boolean recursive)
at Infragistics.Win.UIElement.DrawHelper(Graphics graphics, Rectangle invalidRectangle, Boolean doubleBuffer, AlphaBlendMode alphaBlendMode, Boolean clipText, Boolean forceDrawAsFocused, Boolean preventAlphaBlendGraphics)
at Infragistics.Win.ControlUIElementBase.Draw(Graphics graphics, Rectangle invalidRectangle, Boolean doubleBuffer, AlphaBlendMode alphaBlendMode, Size elementSize, Boolean preventAlphaBlendGraphics)
at Infragistics.Win.ControlUIElementBase.Draw(Graphics graphics, Rectangle invalidRectangle, Boolean doubleBuffer, AlphaBlendMode alphaBlendMode)
at Infragistics.Win.UltraControlBase.OnPaint(PaintEventArgs pe)
at System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, Int16 layer, Boolean disposeEventArgs)
at System.Windows.Forms.Control.WmPaint(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
I've never seen this exception before in my own testing.
A bit of searching turned up the following article from Microsoft, suggesting that this may be an issue with the .NET Framework itself:http://support.microsoft.com/?id=312544
This article gives some troubleshooting tips, and links to a hotfix that may address the problem.
Please let us know if this addresses your issue.