-
Logged In: YES
user_id=919791
The compiler it is looking for is the Help2 compiler for
the 'VS.NET' documenter.
This is part of the "Visual Studio 2005 SDK"...
If you don't need to create Help2 docs to integrate into
VS, then remove the "VS.NET" documenter from the solution.
2006-01-19 16:40:34 UTC in NDoc
-
Logged In: YES
user_id=919791
v2.0.50727.
2005-12-31 04:06:00 UTC in NDoc
-
I suspect the problem is the ampersand(&) in the code. Remenber that the doc comments must be valid xml, and that the ampersand is a reserved character in xml.
The simplest solution is to enclose the contents of the <code> tag in an xml CDATA block.
2005-12-08 19:13:05 UTC in NDoc
-
The format you have shown *should* work...
I would suggest the following steps;
1. Check there are no compiler warnings - sometimes the c# compiler seems to think the enum comments are invalid. If this happens, and the enum definition is in the same file as another type, try moving it to it's own file. If the enum is nested, try moving it to a differant location within the containg type.
2005-12-08 19:04:03 UTC in NDoc
-
Logged In: YES
user_id=919791
Up again :-)
2005-12-02 15:15:59 UTC in NDoc
-
Logged In: YES
user_id=919791
NDoc is working 'by design'.
If you set SkipNamespacesWithoutSummaries then any
namespace *and* it's contained types are not documented if
there is not namespace summary. If this namespace is the
only one in the project, then *no* types will be
documented, and NDoc will raise the exception you
described. The exception description could be enhanced...
2005-12-02 15:14:16 UTC in NDoc
-
Logged In: YES
user_id=919791
As you pointed out, this is a bug in J#... As such, there
is little or nothing we can do to resolve the issue;
without the full signature, NDoc cannot match
documentation against the assembly metadata. I suppose
NDoc could be modified to 'best guess' the match, but I
think this would be at best a hack and at worst produce
incorrect documentation :-(.
2005-12-02 15:07:37 UTC in NDoc
-
The html help sdk is pretty old, and the installer tries to 'upgrade' the html help viewer - but most systems have already got a newer version through service packs etc. No harm done... Ithe compiler is the important bit :-)
Your file locking problem *may* be caused by a search indexing system holding a file or directory open (even if the indexer has paused). Try re-running NDoc, as the lock...
2005-11-14 14:36:05 UTC in NDoc
-
The HTML Help compiler is not part of the NDoc install, but is freely available from Microsoft at
http://msdn.microsoft.com/library/en-us/htmlhelp/html/hwMicrosoftHTMLHelpDownloads.asp.
2005-11-14 12:44:25 UTC in NDoc
-
If none of your comments are appearing, then NDoc is probably not reading the xml file.
Check that it is declared in the NDoc project by selecting the assembly, and click edit;make sure the xml file correctly specified...
To answer your other question; all comments should be 'well-formed' xml. This means that any occurence of an xml reserved character must be properly escaped, and all tags...
2005-10-19 13:23:03 UTC in NDoc
