NDocProc updated for C# 2.0 with Generics
November 7th, 2007 tonyg
NDocProc, our small and simple .NET javadoc-like documentation generator, has been updated for C# 2.0 and Generics.
Changes since the previous announcement include:
- Support for generics, nested types, arrays, delegates, events, and the intersection of them all.
- Now requires .NET 2.0 or Mono 2.0 to build.
- Support for slightly more of the XML documentation language used in .NET documentation comments.
- Better formatting of namespace pages, and summaries on the main index page.
The project homepage is here. You can download a zip of the latest version, or use darcs to check out the repository:
darcs get http://www.lshift.net/~tonyg/ndocproc/
Entry Filed under: Technology, Tools, Our Software
5 Comments Add your own
1. Claus | January 14th, 2008 at 3:05 am
Change this code in “Reflection”:
foreach (Type t in a.GetTypes())
{
if (t.Namespace == null)
continue;
if (!namespaces.ContainsKey(t.Namespace))
{
namespaces[t.Namespace] = new ArrayList();
}
((ArrayList)namespaces[t.Namespace]).Add(t);
types[t.FullName] = t;
}
2. tonyg | January 14th, 2008 at 12:36 pm
Hi Claus,
Thanks for the contribution! What’s the motivation behind the change?
3. Claus | January 18th, 2008 at 2:46 am
In my project, the key ‘t.Namespace’ was noy in the list. So I got an exception at ‘namespaces[t.Namespace]=….
BTW: I always do this checking with Arrays.
4. tonyg | January 21st, 2008 at 12:32 pm
So, it turns out that in yet another design masterstroke, MS have decreed that null shall not be permitted as a key in an IDictionary. Thanks for the heads-up, Claus. I shall work around the issue and release another snapshot.
5. tonyg | January 21st, 2008 at 1:12 pm
I’ve released an update to NDocProc which fixes the bug, Claus. Please let me know if it works for you! … and thanks for the bug report.
Leave a Comment
Some HTML allowed:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>
Trackback this post | Subscribe to the comments via RSS Feed