I have about 30 controls that I have been porting from 1.1 to 2.0 and have run into several issues that I hope someone can provide an answer to.
Note that I am familiar with the basic design, the xmta and all the attributes therin and the design time dll.
1) I haven't been able to get a component type control to work at all (one that appears in the component tray)
2) I can find no way to block controls from appearing in the toolbox in the VS designer. I have controls that are base classes for other controls. They have to be a control, but should not show in the toolbox.
3) I have toolboxbitmap issues. Sometimes they show up, sometimes not. When they do the bitmaps don't seem to be rendering in the same manner as 1.1.
4) It appears that support classes, like classes for expandable property types must be marked with the DesktopCompatible attribute in order to work properly, moe of an observation than a question I guess.
Any input would be appreciated.
Thanks
Bill
CF 2.0 Controls
ForestMax
Not much action on this question. Thought I'd post a follow up on the progress made ( and some not made) on a few fronts.
1) I do have a component control working. SOME of them do not work, but I anticipate I'll find specific problems with each of those.
2) There is no way that I can find to control whether the component shows in the VS toolbox or not, other than making it inherit from something besides Component. I sure could use some kind of solution for this.
3) Toolbox bitmaps are still pretty flakey while I am changing the dll. I have to exit and reenter VS to get them to show up sometimes. No components were showing up when I deployed the dll. I cut the controls back to a bare minimum and began adding a few at a time and testing as I go. So far that has worked, I'm hoping to discover what killed the distribution of the dll. Also, interstingly it seems like the color black is masked out, that's why the toolbox items looked different. Replacing black with a dark blue got them looking fairly normal again.
A new thing that has cropped up is a problem with custom type converters. I can get custom designers, custom UI Editors and even a custom CodeDomSerializer to work. I can't get ANY of the custom type converters to work. They all have problems and end up crashing VS. Note that type converters from MS dlls seem to work OK.
Toolbox visibility and type converters are my biggest problem right now.
Thanks for any input.