Something strange has happened on my machine.

I tried using n UltraListView this afternoon for the first time ever and was surprised to see it land in the Form's  Component Tray.  I'd read up on the object and was sure it is a control, not a component.

After trying the same thing in a brand new, clean Windows Forms project, I gave up when the same thing behaviour repeated every time.  I decided that there was soemthing odd about that type of object and went on to some other work.

Later on, when I dragged an UltraGrid onto my form and saw it land in the Component Tray, I realized that something could be generally amiss.

I've since played with a dozen other controls and half of them are acting as components.

At some point after the first UltraViewList acted odd, I used Document Outline to try and move the object into a different container on my form; into an ExpandableGroupBox.  This caused VS to crash.  Of course, I tried that a second time after restarting VS and met with the same fate.

This morning, I installed the latest hotfix (NetAdvantage_20083_CLR2X_WIN_HotFix_2039).  Tomorrow, we're going to see if the same behaviour is occurring on another dev machine.

In the meantime, here is a list of the controls that I've tried, grouped into those that function correctly, and those that don't.

Does anybody see a pattern that might suggest a simple fix?

Thanks.

Those that behave properly:
...Misc.UltraButton
...Misc.UltraExpandableGroupBox
...Misc.UltraLabel
...UltraWinEditors.UltraDateTimeEditor
...UltraWinEditors.UltraWinCalc.UltraCalculator
...UltraWinSchedule.UltraDayView
...UltraWinSchedule.UltraMonthViewSingle
...UltraWinStatusBar.UltraStatusBar

Those that end up in Component Tray:
...FormattedLinkLabel.UltraFormattedLinkLabel
...FormattedLinkLabel.UltraFormattedTextEditor
...UltraWinGauge.UltraGauge
...UltraWinGrid.UltraDropDown
...UltraWinGrid.UltraGrid
...UltraWinListView.UltraListView
...UltraWinTree.UltraTree