Red "X" displayed instead of controls

[AddAdd]

i have a form on which we have a bunch of controls when the form is
loaded the panels & radio buttons are not displayed but red rectangles
with "X" accross them are put in its place. this behavior is not
consistent except for on one customer site accross the entire citrix
farm & stand alone PCs

any help would be appricated

thanks

 

[Frans Bouma [C# MVP]]

i have a form on which we have a bunch of controls when the form is
loaded the panels & radio buttons are not displayed but red rectangles
with "X" accross them are put in its place. this behavior is not
consistent except for on one customer site accross the entire citrix
farm & stand alone PCs

red crosses in controls mean one thing: an exception occured while the
control was interacting with the bound objects. As in general the .NET
vanilla controls swallow exceptions or don't give much info what
happened, it can be a pain to track down what happened, but as it
happens in one occasion, it might be easily trackable now you know an
exception occured during databinding (thus when the control read the
data from the bound controls)

FB

--
------------------------------------------------------------------------
Lead developer of LLBLGen Pro, the productive O/R mapper for .NET
LLBLGen Pro website: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------

 

[AddAdd]

none of the controls on the form are databound....

 

[Brian Gideon]

Like Frans said this happens when an exception occurs while the control
is processing one of the windows messages. It's probably WM_PAINT. At
least that's where I've seen it before. In that particular case I
determined the problem was caused by another thread accessing the
control. Controls can only be accessed from the thread that created
them. I don't know if that's causing the problem in your case, but
it's something to consider.

Brian

 

[ADDSys]

thatks, that pointed me in the right direction, it seems that one of
teh 3rd party control (farpoint spread) we are using was changing the
threading model. this was working fine untill we upgraded to VS2005
which caused all sorts of hell with COM interop....