I have this basically completed using DocProject back-ended with SandCastle under the hood.
The remaining tasks are: - convert the vs-integrated help file compilation to a command-line invocation that's build-script-invokable - customize the graphics, color, etc. of the output HTML for the web-based version of the API reference - puzzle out the best way to include/deploy the dependencies (probably in \TOOLS\) needed for successful invocation of SandCastle-based projects - commit the above work to the 2.1 branch I would anticipate being able to complete this over the coming weekend without any troubles. Steve Bohlen [email protected] http://blog.unhandled-exceptions.com http://twitter.com/sbohlen On Thu, Jul 2, 2009 at 11:07 AM, Tuna Toksoz <[email protected]> wrote: > and i know that ndoc2 is not for api documentation :) > > Tuna Toksöz > Eternal sunshine of the open source mind. > > http://devlicio.us/blogs/tuna_toksoz > http://tunatoksoz.com > http://twitter.com/tehlike > > > > > On Thu, Jul 2, 2009 at 6:06 PM, Tuna Toksoz <[email protected]> wrote: > >> What is the progress on this? I can try integrating sandcastle command >> line thing into the trunk as ndoc2 is throwing on me at the moment. >> >> Tuna Toksöz >> Eternal sunshine of the open source mind. >> >> http://devlicio.us/blogs/tuna_toksoz >> http://tunatoksoz.com >> http://twitter.com/tehlike >> >> >> >> >> >> On Mon, Mar 30, 2009 at 4:51 PM, Stephen Bohlen <[email protected]>wrote: >> >>> >>> Since I wasnt working w the NH source but rather the binaries, I was >>> testing purely in VS and not considering that (of course) the build scripts >>> = the way NH gets compiled ra >> >> >> >
