>>I'm not sure I'm following. Isn't the original question about scope of the enum? And Naomi's reluctance to make it public?
>>
>>>>I read an interesting blog post several years ago talking about how to test "hidden" functionality in a class. The summary was to just make everything public, since you really should be developing against an interface instead of the implementation. You can achieve your hidden visibility goal though the interface.
>>>
>
>I actually already found the solution. I just needed to use ClassName.EnumName to make it work.

Umm. But that's what you always need to do - a nested enum is not an instance member of a class.