Looks good.Would really like to see a fully user configurable magic comment marker.My own document generator uses '///' :)And "NO!" it will never be released into the wild - it's way too personalised to my way of doing things :PBesides which it's largely written in SED and AWK, with a bit of Perl thrown in for good measure.

@Robin L-Mitchell Would really like to see a fully user configurable magic comment marker.

I went back and forth with the idea of making it configurable, and at one point it was. What concerned me, and maybe I was over thinking it, was that if multiple people were sharing code, and all used their own marker, then documenting the shared code wouldn't work. But would you be documenting other people's code? If you were, couldn't you agree on a marker? But what if you already had a lot of your own code marked your way? What if you used some of the same code, shared with different people who all used different markers? (See what I mean by over thinking?)

Sure :)I have seen teams use three documentation 'markers'; Personal, Team and Project. Only the Project marker was intended for resolving by an automated documentation system. Of course people would forget to change markers, or use the wrong one. But that is no worse than checking in multiple fixes in one shot, or forgetting to comment check-ins at all!

@Dirk C Finally got around to sending you an email with 2 bugsI attached a demo project showing the bugs to the e-mail.

Markdown does not seem to get processed on WindowsTables after the details section have a wrongly highlighted first line. (can be fixed by manually editing the css file)

I posted 2.0a12, it should fix the the css issue in the template that messes up the table headings. I couldn't reproduce the markdown issue, but I did update the code that finds the helper - hopefully that will help.

(There have been a number of other changes since the last public 2.0a5, see the release notes page)