--- Scott Hernandez [EMAIL PROTECTED] wrote:
Right now the Task References are created by NDoc
via the userdoc target.
The product of this process doesn't seem to be getting
checked in. The net result is, when you check out the
docs from CVS, the core part of the documentation (the
tasks
as
html? (it should not be
edited in that form)
- Original Message -
From: Jeffrey McManus [EMAIL PROTECTED]
Sent: Thursday, January 23, 2003 2:51 PM
--- Scott Hernandez [EMAIL PROTECTED] wrote:
Right now the Task References are created by
NDoc
via the userdoc target
--- Scott Hernandez [EMAIL PROTECTED] wrote:
The source in cvs does represent the documentation
at any point, not the
other way around. What your suggesting would lead to
ever more dissimilarity
between a build and the docs in the system. We would
need to check in new
docs whenever a source
Having docs checked in makes sense if they are
edited as html. Ours are
generated. We should be updating the website
regularly with the latest
docs. Perhaps the nightlies should include this too.
Updating the website with documentation on features
that aren't in the latest stable build
--- Scott Hernandez [EMAIL PROTECTED] wrote:
Oh. It sounds so simple, but this lever of
automation we do not have. It
would require cvs polling, or a linux build
environment on sourceforge.net.
Yep, I didn't mean it seriously -- hence the smiley
after the suggestion. (Although...I'm not super
There's an HTML error at the bottom of the page
describing the 'nunit' task
(http://nant.sourceforge.net/help/tasks/nunittask.html).
This error occurs in both IE 6.0 and Mozilla
(Phoenix). It looks like the page wants to document an
attribute of the nunit task, but it got munged
somehow? Anyway.
I'm happy to contribute as much as I can to docs; I've
synched everything up with CVS and I'll start looking
at them tonight. With your permission, one of things
I'd like to start thinking about is a short
introductory blurb/doc that introduces the concept of
a build tool at a high level for
