Just an update on CLS compliance - we are using RadControls for WinForms Q1 2008 SP1 (version 188.8.131.52) and many of the DLLs still do not declare if they are CLS compliant or not (so default to false)
DLLs marked compliant=true:
DLLs not marked at all (i.e. default to false):
Note that these DLLs are not explicitly declared as non-compliant, they contain no declaration at all (so are treated as not compliant).
Best practice (i.e. FXCop) is to at least explicitly mark as either CLS compliant or not (leaving unmarked is just sloppy).
They probably are CLS compliant, unless you use a lot of unsigned values, override operators without providing an alternative or double up on members whose names only differ by case.
All of these are bad practices that will hinder interoperability with the widest range of .NET languages and so should be avoided anyway, so they probably are not being used and it was simply lack of attention to detail to not mark the assemblies as CLS compliant.
Not a big issue, but it would be nice to get them fixed and reduce the amount of unneeded warnings.