thanks marina, i'm actually using NDoc for developer documentaion at
this point (how to use the class libraries (.ddl)). i structure our
code with the XML notation you speak of (/// for c#). but building user
type documentation (how to use the product), is a different story.
by the way, i am able to use the NDoc executable, but i had to add the
following to a NDocGui.exe.config file, which is parallel to the NDoc
executable...where the version is set to whatever you have.
<configuration>
<startup>
<supportedRuntime version="v2.0.50727" />
</startup>
</configuration>
-
jen
If you type in three apostrophes in a row above a class or class
member,
etc. VS will default some XML documentation comment tags. Fill in the
tags,
compile, and this will provide intellisense when you use the assembly
elsewhere.
As for documentation, the only thing I am aware of that is free and
produces
documentation is NDoc. You can google for it. It is capable of
creating
HTML files and CHM files which look pretty nice. The only weird thing
is,
for 2005, you need to download the source for NDoc, compile it, and
then run
the executable. The executable off their download site doesn't actually
work
and ends up throwing exceptions.
i'm trying to decide what format to use when it comes to building
user
help and tips.
.chm files, tooltips, custom forms, other...? is there a tool that
"easily" lets you build
help files (.chm, etc..)?
thanks to those who reply...i appreciate the input!