Thanks Adam,

I did try removing 5.2 and replacing with 5.3, but no luck.

FYI, it seems that even though we're seeing the error in the CuteEditor, another commercial component in the app (VM.xPort.DS2XL) may be the source of the namespace collision. We're going to try rearranging our namespaces to accomodate this control & see if that will at least temporarily resolve the exceptions.

For what it's worth, this seems to be an issue with Dotfuscator output on quite a few commercial components, and I would consider bringing it to their attention. Apparently, any combination of two or more controls that use Dotfuscator  and the System.ComponentModel.Licensing model will cause namespace collisions if any one of them fails to insulate its namespace properly. In every case I've seen, Dotfuscator assigns the name "a" to the class which inherits from LicenseProvider.

I would consider that a significant shortcoming in the Dotfuscator product; it make for components that are prone to conflicts, and it's also not very strong obfuscation if the output is that deterministic.

Thanks again; I'll post any further findings here as they might help other users avoid this issue.