Thank you very much for your feedback. This has definitely been one of the more disscused
issues in the past. People generally fall (passionately) on one side of the debate or the other (you'll notice I was on the multiple assembly side back in February of last year), but we are confident that a single assembly is the best approach for "Prometheus".
The biggest advantage of the single assembly, as you guessed, is a simplified deployment scheme. With a single assembly- and no RadControls directory necessary- deployment will be a simple matter of adding a single DLL to your bin (or GAC) to gain access to all "Prometheus" controls.
Internally, a single assembly also offers a number of benefits to the dev teams that will ultimately benefit you (the developers). A single assembly will allow the controls to easily share common resources, which in turn will help make the "Prometheus" control APIs more consistent from control to control. A single assembly will also help the dev teams ensure to a greater level that all controls "play nice" together an avoid some of the issues with conflicting controls that have been experienced in the past.
All of that said, we definitely want to hear your feedback about working with the single assembly. I know there is some fear of being forced to upgrade all or nothing, but in my own experience I've usually found that when I upgrade the controls in a project I upgrade everything at one time. Let us know how your early tests with the controls go and definitely keep the feedback coming as continue the "Prometheus" beta!