Bugzilla – Bug 316486
monodoc treats nested classes oddly
Last modified: 2007-09-15 21:24:40 UTC
---- Reported by danw@gnome.org 2004-11-18 15:43:28 MST ---- If you have namespace Foo { class One { ... } class Two { class Nested { ... } } } monodoc will generate/expect doc files named Foo/One.xml Foo/Two.xml Foo/Nested.xml But if you then add either "Foo.Nested" or "Foo.One.Nested" to the namespace, you'll lose, because there'll be a naming conflict. ---- Additional Comments From sebastien@ximian.com 2004-11-18 22:26:55 MST ---- #60826 (public nested class are listed in the documentation even if the parent class isn't public) is another issue with nested class. ---- Additional Comments From miguel@ximian.com 2004-11-29 22:35:44 MST ---- Ben, can you look at these two? ---- Additional Comments From bmaurer@users.sf.net 2004-11-30 19:53:42 MST ---- Fixed, but we will need someone to update the docs we have (the updater will do it, but it needs some svn magic) Unknown operating system unknown. Setting to default OS "Other".