Hi.  I have started to use the <ndoc> task as part of my build process.  I am currently using the MSDN documenter.  However, there is a problem with the Namespace Hierarchy pages.  When you click the Namespace Hierarchy link at the top of the page, you are given a page with a list of namespaces in the project, as normal.  However, they all point to the MSDN SDK documentation.  Classes like System.Object work fine on this page, since the SDK documentation has pages for those.  But whenever I try one of my own classes, it brings up a page not found error.

 

This is my current setup for the MSDN documenter (though I’ve tried tweaking these settings many times to no avail):

 

<documenter name="MSDN">

<property name="OutputDirectory" value="${build.out}\doc\MSDN" />

      <property name="HtmlHelpName" value="Puffin" />

      <property name="IncludeFavorites" value="False" />

      <property name="Title" value="An NDoc Documented Class Library" />

      <property name="IncludeAssemblyVersion" value="True" />

<property name="Preliminary" value="True"/>

<property name="DocumentAttributes" value="True" />

</documenter>

 

Is anyone currently having this problem?  Does anyone know of a setup that works?  I’m using the 24-Oct-2004 23:35 build of Nant.

 

Thanks v much

 

John

*************************************************************************************
Privileged/Confidential Information may be contained in this
message. If you are not the addressee indicated in this
message (or responsible for delivery of the message to such
person), you must not copy, distribute or take any action in
reliance to it.
In such case, you should destroy this message and kindly
notify the sender by reply email. Please advise immediately
if you or your employer do not consent to Internet email for
messages of this kind. Opinions, conclusions and other
information in this message that do not relate to the official
business of Minorplanet Systems Plc shall be understood as
neither given nor endorsed by it.
***********************************************************************

Reply via email to