I do not agree, the DotNet controls are thread safe as long as you don't use the same control from within different threads. But if you have different threads each referencing a seperate controls, there won't be any problem.

The problem here is that the infragistics components are not thread safe even if seperate threads use seperate controls.

I'm not sure what you mean by "isl file", I don't know what that is, nor do I use that.

I just have seperate threads calling a constructors on seperate form's initializecomponent, and occasionally the exception mentionned is displayed.

Michael

Hi Michael,

Can you post a small sample project which reproduces the exception so we can check this out? It may be a bug in AppStyling.

Hey Mike,

I have so far been unable to reproduce this error with a sample application.

Does the exception itself provide any opportunity to track the problem or give me information under what conditions it could occur ?

Kind regards,

Michael

Hi,

I just wanted to know if you were able to solve your issue based on Mike's suggestions or you still need help? Just let me know.

Thank you.

Hey,

I was not able to solve the issue. I haven't managed to reproduce the problem in a sample application. With Mike's suggestions I can try again and work the other way around, starting from the current application and stripping it down to the bare essentials. However I currently don't have time to do that, maybe I will next week.

This issue is very important to us as we hope to help increase performance by preloading all the views in our applications. So I will defenitely keep testing till I can reproduce and track down this problem.

Kind regards,

Michael

Hello, ­­­­­

I am just checking about the progress of this issue. Let me know If you need our further assistance on this  issue?

Thank you for using Infragistics Components.

I believe I have now resolved this issue.

Two different patch versions of the v11.1 DLLs were being loaded. When the second copy tried to initialize the style data, the exception was thrown.

Hristo,

I'm also seeing this issue. Stacktrace:

System.ArgumentException: An item with the same key has already been added.

   at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)

   at Infragistics.Win.AppStyling.StyleUtilities.StyleHashtable`2.Add(TKey key, TValue value)

   at Infragistics.Win.AppStyling.StyleUtilities.UpdateRoleHierarchy(StyleHashtable`2 table, AssemblyStyleInfo[] assemblyInfos)

   at Infragistics.Win.AppStyling.StyleManager.ProcessLoadedAssembliesImpl()

   at Infragistics.Win.AppStyling.StyleManager.ProcessLoadedAssemblies()

   at Infragistics.Win.AppStyling.StyleManager.GetSharedObjectProperties(String sharedObjectName)

   at Infragistics.Win.AppStyling.StyleManager.SharedObjectCache.GetProperties()

   at Infragistics.Win.AppStyling.StyleManager.PropertyInfoCache.ParseProperty(String propertyName)

   at Infragistics.Win.AppStyling.StyleManager.PropertyInfoCache.GetProperty(String propertyName)

   at Infragistics.Win.AppStyling.StyleManager.GetSharedObjectPropertyValue(ComponentRole componentRole, String sharedObjectName, String propertyName)

   at Infragistics.Win.AppStyling.ComponentRole.GetProperty(String sharedObjectName, String propertyName)

   at Infragistics.Win.UltraWinScrollBar.ScrollBarStyleInfo.get_ViewStyleResolved()

   at Infragistics.Win.UltraWinScrollBar.ScrollBarUIElement.get_BorderStyle()

   at Infragistics.Win.UIElement.get_RectInsideBorders()

   at Infragistics.Win.UltraWinScrollBar.ScrollBarUIElement.PositionChildElements()

   at Infragistics.Win.UIElement.VerifyChildElements(ControlUIElementBase controlElement, Boolean recursive)

   at Infragistics.Win.UIElement.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.UIElement.Draw(Graphics graphics, Rectangle invalidRectangle, Boolean doubleBuffer, AlphaBlendMode alphaBlendMode, 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, Size elementSize)

   at Infragistics.Win.ControlUIElementBase.Draw(Graphics graphics, Rectangle invalidRectangle, Boolean doubleBuffer, AlphaBlendMode alphaBlendMode)

   at Infragistics.Win.UltraControlBase.OnPaint(PaintEventArgs pe)

   at Infragistics.Win.UltraWinTree.UltraTree.OnPaint(PaintEventArgs pe)

   at System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, Int16 layer)

   at System.Windows.Forms.Control.WmPaint(Message& m)

   at System.Windows.Forms.Control.WndProc(Message& m)

   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

In this case, it happens when a drop-down custom control, containing other Infragistics elements (in this case, an UltraTextEditor, UltraDropDownButton, UltraPopupControlContainer and an UltraTree.

I'm not sure that I'll be able to produce a simple test case, sadly. However, if I can narrow down what's causing this, I'll let you know.