You can do that easily with a macro or add-in, iteraring the files as
explained in my article:
HOWTO: Navigate the files of a solution from a Visual Studio .NET macro or
add-in
http://www.mztools.com/articles/2006/MZ004.htm
and for each ProjectItem, you use ProjectItem.Fil eCodeModel.Code Elements and
iterate the code elements recursively.
There is already a built-in feature in my add-in (below) that can help you:
the Generate XML/HTML documentation feature. It works generating a XML file
with all the information of your code. Then you can use a XSLT file to
filter the content and render it as HTML.
If you need help with either approach let me know.
--
Best regards,
Carlos J. Quintero
MZ-Tools: Productivity add-ins for Visual Studio
You can code, design and document much faster:
http://www.mztools.com
"mark" <ma**@discussio ns.microsoft.co m> escribió en el mensaje
news:55******** *************** ***********@mic rosoft.com...
I have a very large class library and I need to provide documentation. I
need
a list of all methods but I don't need the underlying code so the collapse
to
definitions form is great. However, if I copy the code editors contents
when
it is collapsed then paste it into MS Word it expands into full code.
Any thoughts?
--
mark b