Current best practices state that you should associate your code as closely
with the documentation as possible. This has been a best practice for
better part of a decade. There is even a branch of computer science called
Literate Programming where the code is extracted from the documentation, not
the other way around.
If you don't want to look at the documentation, you can always collapse it.
When you create a standard code block, Visual Studio gives one of those
little "-" controls in the left margin. If you hit it, the documentation
collapses.
--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik
Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
--
"Matthijs ter Woord" <ma**************@gmail.com> wrote in message
news:O1*************@TK2MSFTNGP14.phx.gbl...
Hi,
I want to document my class libraries' API's. They're all in C#. I could
use
the inline documentation comments, but I feel, using inline documentation
comments makes the source code messy. Are there any opensource tools which
allow me to document my library without using the source code?
Greets,
Matthijs ter Woord