By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,203 Members | 1,620 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,203 IT Pros & Developers. It's quick & easy.

Source code documentation

P: n/a
GTi
Is there any source code documentation tools available for Visual
Studio 2005 ?
I have created a LIB that must be documented. Must I do it by hand or
is it
some kind of tools to pre document my source code?

Mar 4 '06 #1
Share this Question
Share on Google+
40 Replies


P: n/a
Hi GTi,
I was looking into the issue a few weeks ago. From what I found NDoc at
present only has partial support for .Net 2.0, doesn't seem to be any
definitive date on when it will have full support. The only other option I
found was a company called Inovasys (www.innovasys.com) who have a product
called Document X which will be fully compable with 2.0 by then end of this
month. At the moment they do have a beta but it is only available to
existing companies. So if you can wait a few weks this may be worth checking
out. It is a commercial product so it is not free if that is one of your
main criteria.

Hope that helps
Mark Dawson
http://www.markdawson.org
"GTi" wrote:
Is there any source code documentation tools available for Visual
Studio 2005 ?
I have created a LIB that must be documented. Must I do it by hand or
is it
some kind of tools to pre document my source code?

Mar 4 '06 #2

P: n/a
GTi
Mark,
Tx for the feedback.

Mar 4 '06 #3

P: n/a
There is built-in XML Documentation Comment support in Visual Studio.Net
2005. Here's an example of what I did with it:

http://www.dynamicsystems.com/weathe...al.Weather.htm

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer

Presuming that God is "only an idea" -
Ideas exist.
Therefore, God exists.

"GTi" <tu****@gmail.com> wrote in message
news:11**********************@p10g2000cwp.googlegr oups.com...
Is there any source code documentation tools available for Visual
Studio 2005 ?
I have created a LIB that must be documented. Must I do it by hand or
is it
some kind of tools to pre document my source code?

Mar 4 '06 #4

P: n/a
On Sat, 4 Mar 2006 10:25:52 -0500, "Kevin Spencer"
<ke***@DIESPAMMERSDIEtakempis.com> wrote:
There is built-in XML Documentation Comment support in Visual Studio.Net
2005.


There is!? Where? I was firmly convinced that this 2003 feature was
taken out of 2005 -- can you tell me the exact menu location?
--
http://www.kynosarges.de
Mar 4 '06 #5

P: n/a
Hello Christoph,

Kevin means that you can get XML documentation, not the chm compiled as NDoc
did.
To turn this on go to the project properties->Build panel-> check "XML Documentation
file"

to be shure that every method/class has been documented check "treat warnings
as error" on ALL

CN> On Sat, 4 Mar 2006 10:25:52 -0500, "Kevin Spencer"
CN> <ke***@DIESPAMMERSDIEtakempis.com> wrote:
CN>
There is built-in XML Documentation Comment support in Visual
Studio.Net 2005.

CN> There is!? Where? I was firmly convinced that this 2003 feature was
CN> taken out of 2005 -- can you tell me the exact menu location?
CN>
---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsche
Mar 4 '06 #6

P: n/a
Are you saying the option in VS2003 Tools->Build Comment Web Pages has been
taken out is VS2005? Wow, I did not know that.....pretty disappointing.

"Michael Nemtsev" wrote:
Hello Christoph,

Kevin means that you can get XML documentation, not the chm compiled as NDoc
did.
To turn this on go to the project properties->Build panel-> check "XML Documentation
file"

to be shure that every method/class has been documented check "treat warnings
as error" on ALL

CN> On Sat, 4 Mar 2006 10:25:52 -0500, "Kevin Spencer"
CN> <ke***@DIESPAMMERSDIEtakempis.com> wrote:
CN>
There is built-in XML Documentation Comment support in Visual
Studio.Net 2005.

CN> There is!? Where? I was firmly convinced that this 2003 feature was
CN> taken out of 2005 -- can you tell me the exact menu location?
CN>
---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsche

Mar 4 '06 #7

P: n/a
> Are you saying the option in VS2003 Tools->Build Comment Web Pages has
been
taken out is VS2005? Wow, I did not know that.....pretty disappointing.
It's not really disappointing if you think about it. If you create HTML Code
Comments, you have created an HTML document. Modifying it to suit your own
model of how it should look is a pain in the butt. HTML is simply *not*
extensible.

But if you create XML Code Comments, you can create *any* type of document
from the XML, simply by creating an XSL Transform for it. You can transform
it in any way you like, and change the format with a simple change to the
XSLT that you use to format it. That is what I did in the page I mentioned
earlier in the thread. I created my own XSLT and use it for all of our
in-house code documentation.

This is part of the "new direction" that Microsoft has been taking, and I
welcome it!

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer

Presuming that God is "only an idea" -
Ideas exist.
Therefore, God exists.
"rmacias" <rm*****@newsgroup.nospam> wrote in message
news:35**********************************@microsof t.com... Are you saying the option in VS2003 Tools->Build Comment Web Pages has
been
taken out is VS2005? Wow, I did not know that.....pretty disappointing.

"Michael Nemtsev" wrote:
Hello Christoph,

Kevin means that you can get XML documentation, not the chm compiled as
NDoc
did.
To turn this on go to the project properties->Build panel-> check "XML
Documentation
file"

to be shure that every method/class has been documented check "treat
warnings
as error" on ALL

CN> On Sat, 4 Mar 2006 10:25:52 -0500, "Kevin Spencer"
CN> <ke***@DIESPAMMERSDIEtakempis.com> wrote:
CN>
>> There is built-in XML Documentation Comment support in Visual
>> Studio.Net 2005.
>>

CN> There is!? Where? I was firmly convinced that this 2003 feature was
CN> taken out of 2005 -- can you tell me the exact menu location?
CN>
---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/laflour

"At times one remains faithful to a cause only because its opponents do
not
cease to be insipid." (c) Friedrich Nietzsche

Mar 4 '06 #8

P: n/a
I installed a version of NDoc for 2.0 and it does everything in 2005 AFAICT.
Docs look great. What does it not support?

--
William Stacey [MVP]

"Mark R. Dawson" <Ma*********@discussions.microsoft.com> wrote in message
news:22**********************************@microsof t.com...
| Hi GTi,
| I was looking into the issue a few weeks ago. From what I found NDoc at
| present only has partial support for .Net 2.0, doesn't seem to be any
| definitive date on when it will have full support. The only other option
I
| found was a company called Inovasys (www.innovasys.com) who have a product
| called Document X which will be fully compable with 2.0 by then end of
this
| month. At the moment they do have a beta but it is only available to
| existing companies. So if you can wait a few weks this may be worth
checking
| out. It is a commercial product so it is not free if that is one of your
| main criteria.
|
| Hope that helps
| Mark Dawson
| http://www.markdawson.org
|
|
| "GTi" wrote:
|
| > Is there any source code documentation tools available for Visual
| > Studio 2005 ?
| > I have created a LIB that must be documented. Must I do it by hand or
| > is it
| > some kind of tools to pre document my source code?
| >
| >
Mar 4 '06 #9

P: n/a
I don't think you understood what I said. That is not what I found
disappointing.

In VS 2003, you could use the inline XML Comments to document your code in
the source code files. The compiler would read these XML comments and
generate an XML document with this information. Now VS 2003 had a built in
tool to read this XML Document, and generate an MSDN like web page that has
your code documented.

The idea was, "We have a tool to interpret the XML document and display it
in a web page to document your code. If it does not suit your needs, then
use NDoc or write your own tool (XSLT, etc) to suit your needs."

Now, in VS 2005, the compiler still generates the XML Document and that's
it. Now the idea is "Here's the XML document, now write your own tool to do
as you wish. We will no longer give you a tool do generate a page for you.
You have to do it yourself." And now as an other user stated, NDoc does not
fully support .NET 2.0 XML code genreated comments (I'll have to look into
this to see if this is true).

What I found disappointint is that they took a tool away that reads the XML
Comment document for you. Most of the time, it suited my needs

"Kevin Spencer" wrote:
Are you saying the option in VS2003 Tools->Build Comment Web Pages has
been
taken out is VS2005? Wow, I did not know that.....pretty disappointing.


It's not really disappointing if you think about it. If you create HTML Code
Comments, you have created an HTML document. Modifying it to suit your own
model of how it should look is a pain in the butt. HTML is simply *not*
extensible.

But if you create XML Code Comments, you can create *any* type of document
from the XML, simply by creating an XSL Transform for it. You can transform
it in any way you like, and change the format with a simple change to the
XSLT that you use to format it. That is what I did in the page I mentioned
earlier in the thread. I created my own XSLT and use it for all of our
in-house code documentation.

This is part of the "new direction" that Microsoft has been taking, and I
welcome it!

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer

Presuming that God is "only an idea" -
Ideas exist.
Therefore, God exists.
"rmacias" <rm*****@newsgroup.nospam> wrote in message
news:35**********************************@microsof t.com...
Are you saying the option in VS2003 Tools->Build Comment Web Pages has
been
taken out is VS2005? Wow, I did not know that.....pretty disappointing.

"Michael Nemtsev" wrote:
Hello Christoph,

Kevin means that you can get XML documentation, not the chm compiled as
NDoc
did.
To turn this on go to the project properties->Build panel-> check "XML
Documentation
file"

to be shure that every method/class has been documented check "treat
warnings
as error" on ALL

CN> On Sat, 4 Mar 2006 10:25:52 -0500, "Kevin Spencer"
CN> <ke***@DIESPAMMERSDIEtakempis.com> wrote:
CN>
>> There is built-in XML Documentation Comment support in Visual
>> Studio.Net 2005.
>>
CN> There is!? Where? I was firmly convinced that this 2003 feature was
CN> taken out of 2005 -- can you tell me the exact menu location?
CN>
---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/laflour

"At times one remains faithful to a cause only because its opponents do
not
cease to be insipid." (c) Friedrich Nietzsche


Mar 4 '06 #10

P: n/a
Hello rmacias,

Where have u found this option? Could you point? I see nothing in my VS 2003

r> Are you saying the option in VS2003 Tools->Build Comment Web Pages
r> has been taken out is VS2005? Wow, I did not know that.....pretty
r> disappointing.
r>
r> "Michael Nemtsev" wrote:
r>
Hello Christoph,

Kevin means that you can get XML documentation, not the chm compiled
as NDoc
did.
To turn this on go to the project properties->Build panel-> check
"XML Documentation
file"
to be shure that every method/class has been documented check "treat
warnings as error" on ALL

CN> On Sat, 4 Mar 2006 10:25:52 -0500, "Kevin Spencer"
CN> <ke***@DIESPAMMERSDIEtakempis.com> wrote:
CN>
There is built-in XML Documentation Comment support in Visual
Studio.Net 2005.

CN> There is!? Where? I was firmly convinced that this 2003 feature
was
CN> taken out of 2005 -- can you tell me the exact menu location?
CN>
---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/laflour
"At times one remains faithful to a cause only because its opponents
do not cease to be insipid." (c) Friedrich Nietzsche

---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsche
Mar 4 '06 #11

P: n/a
It's in the "Tools->Build Comments Web Page" option. I've using VS 2003
Enterprise Developer. The option should be there. It only works with C#
though.

I did a little googling and found out that many customers didn't like it and
it was cut from VS2005. I'll have to find another tool to create my
documentation sites now. The tool in VS2003 suited my needs well. That's
too bad.

"Michael Nemtsev" wrote:
Hello rmacias,

Where have u found this option? Could you point? I see nothing in my VS 2003

r> Are you saying the option in VS2003 Tools->Build Comment Web Pages
r> has been taken out is VS2005? Wow, I did not know that.....pretty
r> disappointing.
r>
r> "Michael Nemtsev" wrote:
r>
Hello Christoph,

Kevin means that you can get XML documentation, not the chm compiled
as NDoc
did.
To turn this on go to the project properties->Build panel-> check
"XML Documentation
file"
to be shure that every method/class has been documented check "treat
warnings as error" on ALL

CN> On Sat, 4 Mar 2006 10:25:52 -0500, "Kevin Spencer"
CN> <ke***@DIESPAMMERSDIEtakempis.com> wrote:
CN>
> There is built-in XML Documentation Comment support in Visual
> Studio.Net 2005.
>
CN> There is!? Where? I was firmly convinced that this 2003 feature
was
CN> taken out of 2005 -- can you tell me the exact menu location?
CN>
---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/laflour
"At times one remains faithful to a cause only because its opponents
do not cease to be insipid." (c) Friedrich Nietzsche

---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsche

Mar 4 '06 #12

P: n/a
I agree with you rmacias, the tool provided in 2003 was more than adequate
for code comments, taking it out in my mind was a great loss, especially if
people are expected to rely on group projects such as NDoc which seems to be
slow in catching up.
"rmacias" wrote:
I don't think you understood what I said. That is not what I found
disappointing.

In VS 2003, you could use the inline XML Comments to document your code in
the source code files. The compiler would read these XML comments and
generate an XML document with this information. Now VS 2003 had a built in
tool to read this XML Document, and generate an MSDN like web page that has
your code documented.

The idea was, "We have a tool to interpret the XML document and display it
in a web page to document your code. If it does not suit your needs, then
use NDoc or write your own tool (XSLT, etc) to suit your needs."

Now, in VS 2005, the compiler still generates the XML Document and that's
it. Now the idea is "Here's the XML document, now write your own tool to do
as you wish. We will no longer give you a tool do generate a page for you.
You have to do it yourself." And now as an other user stated, NDoc does not
fully support .NET 2.0 XML code genreated comments (I'll have to look into
this to see if this is true).

What I found disappointint is that they took a tool away that reads the XML
Comment document for you. Most of the time, it suited my needs

"Kevin Spencer" wrote:
Are you saying the option in VS2003 Tools->Build Comment Web Pages has
been
taken out is VS2005? Wow, I did not know that.....pretty disappointing.


It's not really disappointing if you think about it. If you create HTML Code
Comments, you have created an HTML document. Modifying it to suit your own
model of how it should look is a pain in the butt. HTML is simply *not*
extensible.

But if you create XML Code Comments, you can create *any* type of document
from the XML, simply by creating an XSL Transform for it. You can transform
it in any way you like, and change the format with a simple change to the
XSLT that you use to format it. That is what I did in the page I mentioned
earlier in the thread. I created my own XSLT and use it for all of our
in-house code documentation.

This is part of the "new direction" that Microsoft has been taking, and I
welcome it!

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer

Presuming that God is "only an idea" -
Ideas exist.
Therefore, God exists.
"rmacias" <rm*****@newsgroup.nospam> wrote in message
news:35**********************************@microsof t.com...
Are you saying the option in VS2003 Tools->Build Comment Web Pages has
been
taken out is VS2005? Wow, I did not know that.....pretty disappointing.

"Michael Nemtsev" wrote:

> Hello Christoph,
>
> Kevin means that you can get XML documentation, not the chm compiled as
> NDoc
> did.
> To turn this on go to the project properties->Build panel-> check "XML
> Documentation
> file"
>
> to be shure that every method/class has been documented check "treat
> warnings
> as error" on ALL
>
> CN> On Sat, 4 Mar 2006 10:25:52 -0500, "Kevin Spencer"
> CN> <ke***@DIESPAMMERSDIEtakempis.com> wrote:
> CN>
> >> There is built-in XML Documentation Comment support in Visual
> >> Studio.Net 2005.
> >>
> CN> There is!? Where? I was firmly convinced that this 2003 feature was
> CN> taken out of 2005 -- can you tell me the exact menu location?
> CN>
> ---
> WBR,
> Michael Nemtsev :: blog: http://spaces.msn.com/laflour
>
> "At times one remains faithful to a cause only because its opponents do
> not
> cease to be insipid." (c) Friedrich Nietzsche
>
>
>


Mar 4 '06 #13

P: n/a
NDoc v1.3 does not support Generics. The nightly build does have generics
capability but is still in alpha.....apparently.

"William Stacey [MVP]" wrote:
I installed a version of NDoc for 2.0 and it does everything in 2005 AFAICT.
Docs look great. What does it not support?

--
William Stacey [MVP]

"Mark R. Dawson" <Ma*********@discussions.microsoft.com> wrote in message
news:22**********************************@microsof t.com...
| Hi GTi,
| I was looking into the issue a few weeks ago. From what I found NDoc at
| present only has partial support for .Net 2.0, doesn't seem to be any
| definitive date on when it will have full support. The only other option
I
| found was a company called Inovasys (www.innovasys.com) who have a product
| called Document X which will be fully compable with 2.0 by then end of
this
| month. At the moment they do have a beta but it is only available to
| existing companies. So if you can wait a few weks this may be worth
checking
| out. It is a commercial product so it is not free if that is one of your
| main criteria.
|
| Hope that helps
| Mark Dawson
| http://www.markdawson.org
|
|
| "GTi" wrote:
|
| > Is there any source code documentation tools available for Visual
| > Studio 2005 ?
| > I have created a LIB that must be documented. Must I do it by hand or
| > is it
| > some kind of tools to pre document my source code?
| >
| >

Mar 4 '06 #14

P: n/a
Hello rmacias,

Got it. I just have never use it :)

I recomend to look at GhostDoc http://www.roland-weigelt.de/ghostdoc/ it
works for VS2005

r> It's in the "Tools->Build Comments Web Page" option. I've using VS
r> 2003 Enterprise Developer. The option should be there. It only
r> works with C# though.
r>
r> I did a little googling and found out that many customers didn't like
r> it and it was cut from VS2005. I'll have to find another tool to
r> create my documentation sites now. The tool in VS2003 suited my
r> needs well. That's too bad.
r>
r> "Michael Nemtsev" wrote:
r>
Hello rmacias,

Where have u found this option? Could you point? I see nothing in my
VS 2003

r> Are you saying the option in VS2003 Tools->Build Comment Web Pages
r> has been taken out is VS2005? Wow, I did not know that.....pretty
r> disappointing.
r>
r> "Michael Nemtsev" wrote:
r>
Hello Christoph,

Kevin means that you can get XML documentation, not the chm
compiled
as NDoc
did.
To turn this on go to the project properties->Build panel-> check
"XML Documentation
file"
to be shure that every method/class has been documented check
"treat
warnings as error" on ALL
CN> On Sat, 4 Mar 2006 10:25:52 -0500, "Kevin Spencer"
CN> <ke***@DIESPAMMERSDIEtakempis.com> wrote:
CN>
>> There is built-in XML Documentation Comment support in Visual
>> Studio.Net 2005.
>>
CN> There is!? Where? I was firmly convinced that this 2003 feature
was
CN> taken out of 2005 -- can you tell me the exact menu location?
CN>
---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/laflour
"At times one remains faithful to a cause only because its
opponents
do not cease to be insipid." (c) Friedrich Nietzsche

---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/laflour
"At times one remains faithful to a cause only because its opponents
do not cease to be insipid." (c) Friedrich Nietzsche

---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsche
Mar 4 '06 #15

P: n/a
On Sat, 4 Mar 2006 16:05:38 -0500, "William Stacey [MVP]"
<wi************@gmail.com> wrote:
I installed a version of NDoc for 2.0 and it does everything in 2005 AFAICT.
Docs look great. What does it not support?


The "a version" you installed was either an alpha test release, or a
modification by another user. There is no public release of NDoc 2.0
on the SourceForge website yet!
--
http://www.kynosarges.de
Mar 5 '06 #16

P: n/a
On Sat, 4 Mar 2006 15:58:19 -0500, "Kevin Spencer"
<ke***@DIESPAMMERSDIEtakempis.com> wrote:
But if you create XML Code Comments, you can create *any* type of document
from the XML, simply by creating an XSL Transform for it. You can transform
it in any way you like, and change the format with a simple change to the
XSLT that you use to format it. That is what I did in the page I mentioned
earlier in the thread. I created my own XSLT and use it for all of our
in-house code documentation.


That's not what anyone thinks of when you say Visual Studio has
"built-in XML Documentation Comment". Please mention additional
custom tools that you're using, we can't read your mind...
--
http://www.kynosarges.de
Mar 5 '06 #17

P: n/a
Hello Christoph,

What do u mean with "additiona custom tools" ?!
Kevin just opened notepad, wrote XSLT schema for VS XML Doc file and he got
a formatted HTML with documented code

CN> On Sat, 4 Mar 2006 15:58:19 -0500, "Kevin Spencer"
CN> <ke***@DIESPAMMERSDIEtakempis.com> wrote:
CN>
But if you create XML Code Comments, you can create *any* type of
document from the XML, simply by creating an XSL Transform for it.
You can transform it in any way you like, and change the format with
a simple change to the XSLT that you use to format it. That is what I
did in the page I mentioned earlier in the thread. I created my own
XSLT and use it for all of our in-house code documentation.

CN> That's not what anyone thinks of when you say Visual Studio has
CN> "built-in XML Documentation Comment". Please mention additional
CN> custom tools that you're using, we can't read your mind...
CN>
---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsche
Mar 5 '06 #18

P: n/a
The XSLT schema that Kevin wrote is a custom tool, and so is the XSLT
processor that he used to generate his web pages.

On Sun, 5 Mar 2006 08:01:36 +0000 (UTC), Michael Nemtsev
<ne*****@msn.com> wrote:
Hello Christoph,

What do u mean with "additiona custom tools" ?!
Kevin just opened notepad, wrote XSLT schema for VS XML Doc file and he got
a formatted HTML with documented code

--
http://www.kynosarges.de
Mar 5 '06 #19

P: n/a
My custom-built "tool" is simply an XSLT file.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer

Presuming that God is "only an idea" -
Ideas exist.
Therefore, God exists.

"Christoph Nahr" <ch************@kynosarges.de> wrote in message
news:eh********************************@4ax.com...
On Sat, 4 Mar 2006 15:58:19 -0500, "Kevin Spencer"
<ke***@DIESPAMMERSDIEtakempis.com> wrote:
But if you create XML Code Comments, you can create *any* type of document
from the XML, simply by creating an XSL Transform for it. You can
transform
it in any way you like, and change the format with a simple change to the
XSLT that you use to format it. That is what I did in the page I mentioned
earlier in the thread. I created my own XSLT and use it for all of our
in-house code documentation.


That's not what anyone thinks of when you say Visual Studio has
"built-in XML Documentation Comment". Please mention additional
custom tools that you're using, we can't read your mind...
--
http://www.kynosarges.de

Mar 5 '06 #20

P: n/a
Hi Michael,

Actually, I used the XSLT Editor and debugging tools in Visual Studio.Net.
But yes, that was about it.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer

Presuming that God is "only an idea" -
Ideas exist.
Therefore, God exists.

"Michael Nemtsev" <ne*****@msn.com> wrote in message
news:9c**************************@msnews.microsoft .com...
Hello Christoph,

What do u mean with "additiona custom tools" ?!
Kevin just opened notepad, wrote XSLT schema for VS XML Doc file and he
got a formatted HTML with documented code

CN> On Sat, 4 Mar 2006 15:58:19 -0500, "Kevin Spencer"
CN> <ke***@DIESPAMMERSDIEtakempis.com> wrote:
CN>
But if you create XML Code Comments, you can create *any* type of
document from the XML, simply by creating an XSL Transform for it.
You can transform it in any way you like, and change the format with
a simple change to the XSLT that you use to format it. That is what I
did in the page I mentioned earlier in the thread. I created my own
XSLT and use it for all of our in-house code documentation.

CN> That's not what anyone thinks of when you say Visual Studio has
CN> "built-in XML Documentation Comment". Please mention additional
CN> custom tools that you're using, we can't read your mind...
CN> ---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/laflour

"At times one remains faithful to a cause only because its opponents do
not cease to be insipid." (c) Friedrich Nietzsche

Mar 5 '06 #21

P: n/a
I can see your point. I don't know why they left it out. I do know that when
I created by XSLT, doing Generics was a bit tricky. Perhaps they didn't have
the time, and it will be available in the future as a downloadable add-on.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer

Presuming that God is "only an idea" -
Ideas exist.
Therefore, God exists.

"rmacias" <rm*****@newsgroup.nospam> wrote in message
news:35**********************************@microsof t.com...
I don't think you understood what I said. That is not what I found
disappointing.

In VS 2003, you could use the inline XML Comments to document your code in
the source code files. The compiler would read these XML comments and
generate an XML document with this information. Now VS 2003 had a built
in
tool to read this XML Document, and generate an MSDN like web page that
has
your code documented.

The idea was, "We have a tool to interpret the XML document and display it
in a web page to document your code. If it does not suit your needs, then
use NDoc or write your own tool (XSLT, etc) to suit your needs."

Now, in VS 2005, the compiler still generates the XML Document and that's
it. Now the idea is "Here's the XML document, now write your own tool to
do
as you wish. We will no longer give you a tool do generate a page for
you.
You have to do it yourself." And now as an other user stated, NDoc does
not
fully support .NET 2.0 XML code genreated comments (I'll have to look into
this to see if this is true).

What I found disappointint is that they took a tool away that reads the
XML
Comment document for you. Most of the time, it suited my needs

"Kevin Spencer" wrote:
> Are you saying the option in VS2003 Tools->Build Comment Web Pages has
> been
> taken out is VS2005? Wow, I did not know that.....pretty
> disappointing.


It's not really disappointing if you think about it. If you create HTML
Code
Comments, you have created an HTML document. Modifying it to suit your
own
model of how it should look is a pain in the butt. HTML is simply *not*
extensible.

But if you create XML Code Comments, you can create *any* type of
document
from the XML, simply by creating an XSL Transform for it. You can
transform
it in any way you like, and change the format with a simple change to the
XSLT that you use to format it. That is what I did in the page I
mentioned
earlier in the thread. I created my own XSLT and use it for all of our
in-house code documentation.

This is part of the "new direction" that Microsoft has been taking, and I
welcome it!

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer

Presuming that God is "only an idea" -
Ideas exist.
Therefore, God exists.
"rmacias" <rm*****@newsgroup.nospam> wrote in message
news:35**********************************@microsof t.com...
> Are you saying the option in VS2003 Tools->Build Comment Web Pages has
> been
> taken out is VS2005? Wow, I did not know that.....pretty
> disappointing.
>
> "Michael Nemtsev" wrote:
>
>> Hello Christoph,
>>
>> Kevin means that you can get XML documentation, not the chm compiled
>> as
>> NDoc
>> did.
>> To turn this on go to the project properties->Build panel-> check "XML
>> Documentation
>> file"
>>
>> to be shure that every method/class has been documented check "treat
>> warnings
>> as error" on ALL
>>
>> CN> On Sat, 4 Mar 2006 10:25:52 -0500, "Kevin Spencer"
>> CN> <ke***@DIESPAMMERSDIEtakempis.com> wrote:
>> CN>
>> >> There is built-in XML Documentation Comment support in Visual
>> >> Studio.Net 2005.
>> >>
>> CN> There is!? Where? I was firmly convinced that this 2003 feature
>> was
>> CN> taken out of 2005 -- can you tell me the exact menu location?
>> CN>
>> ---
>> WBR,
>> Michael Nemtsev :: blog: http://spaces.msn.com/laflour
>>
>> "At times one remains faithful to a cause only because its opponents
>> do
>> not
>> cease to be insipid." (c) Friedrich Nietzsche
>>
>>
>>


Mar 5 '06 #22

P: n/a
I just found this thread. I simply needed a 1-page HTML
documentation package for a component. The original VS2003
'Tools->Build Comment Web Pages ' would have been perfect. Oh well,
now I have to muddle through a bunch of malarky just to get a 1-page
document. It would be faster to edit as an HTML text file except
that I want it to be automatically updatable from the source.

Tried NDoc but I couldn't make it accept my project.

On Sun, 5 Mar 2006 10:43:47 -0500, "Kevin Spencer"
<ke***@DIESPAMMERSDIEtakempis.com> wrote:
Actually, I used the XSLT Editor and debugging tools in Visual Studio.Net.
But yes, that was about it.

So... where is the 'XSLT Editor'? I couldn't find it. Is it
basically the IDE with color tag highlighting and snippets?

How do you translate an XSLT file + XML doco into HTML? I couldn't
find the tool for this, either?

[ I'm sure a million other programmers will have to go through this.
Couldn't MS even supply a sample starting XSLT template?]

Does anyone know of a sample XSLT template from MS or something XSLT
open source?
Mar 13 '06 #23

P: n/a
GTi
I have tested and used the nDoc with Whidbey C# support.
http://ndoc.sourceforge.net/wiki/dotNet_2.0_Support
And it works just fine - some compilling errors but I just ignore them.
It give me a nice MSDN look source doc.

Mar 13 '06 #24

P: n/a
On 13 Mar 2006 14:53:30 -0800, "GTi" <tu****@gmail.com> wrote:
I have tested and used the nDoc with Whidbey C# support.
http://ndoc.sourceforge.net/wiki/dotNet_2.0_Support
And it works just fine - some compilling errors but I just ignore them.
It give me a nice MSDN look source doc.


When did you access that site? I just got this message:

"Could not get visitors lock: Check whether the web server can create
the directory /tmp/persistent/ndoc/wiki/temp and whether it can create
files in it."
--
http://www.kynosarges.de
Mar 14 '06 #25

P: n/a
On Sun, 5 Mar 2006 08:01:36 +0000 (UTC), Michael Nemtsev
<ne*****@msn.com> wrote:
What do u mean with "additiona custom tools" ?!
Kevin just opened notepad, wrote XSLT schema for VS XML Doc file and he got
a formatted HTML with documented code


This makes it sound like Notepad has a 'save as HTML' when editing
an XSLT schema document. ..Clearly this is not the case. Generating
an XSLT file that works properly is complicated enough to rate calling
it an 'additional custom tool'.

While learning XSLT to generate HTML documentation is all a very
interesting exercise, it is way out of the expected C# development and
deployment workflow in an otherwise full-featured Visual Studio 2005.
Mar 14 '06 #26

P: n/a
Hi Jeffery,

The XSL Editor is built into the Visual Studio IDE. When you open an XSL
document in Visual Studio, it is opened in the XSL Editor, even though it
looks much the same as any other type of code file. You will notice that
when the XSL Editor has the focus, there is an "XML" menu item added to the
menu tool bar. You can debug your XSL using this menu item, and generate
HTML from it using the same menu item. You can also insert breakpoints in
the XSL, and perform watches, etc., just like using the Editor to debug
executable code.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer

Presuming that God is "only an idea" -
Ideas exist.
Therefore, God exists.

"Jeffery Jones" <ke**********@newsgroups.nospam> wrote in message
news:8g********************************@4ax.com...
I just found this thread. I simply needed a 1-page HTML
documentation package for a component. The original VS2003
'Tools->Build Comment Web Pages ' would have been perfect. Oh well,
now I have to muddle through a bunch of malarky just to get a 1-page
document. It would be faster to edit as an HTML text file except
that I want it to be automatically updatable from the source.

Tried NDoc but I couldn't make it accept my project.

On Sun, 5 Mar 2006 10:43:47 -0500, "Kevin Spencer"
<ke***@DIESPAMMERSDIEtakempis.com> wrote:
Actually, I used the XSLT Editor and debugging tools in Visual Studio.Net.
But yes, that was about it.

So... where is the 'XSLT Editor'? I couldn't find it. Is it
basically the IDE with color tag highlighting and snippets?

How do you translate an XSLT file + XML doco into HTML? I couldn't
find the tool for this, either?

[ I'm sure a million other programmers will have to go through this.
Couldn't MS even supply a sample starting XSLT template?]

Does anyone know of a sample XSLT template from MS or something XSLT
open source?

Mar 14 '06 #27

P: n/a
Hi Jeffery,

I should mention also that this is only available in VS.Net 2005.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer

Presuming that God is "only an idea" -
Ideas exist.
Therefore, God exists.

"Jeffery Jones" <ke**********@newsgroups.nospam> wrote in message
news:8g********************************@4ax.com...
I just found this thread. I simply needed a 1-page HTML
documentation package for a component. The original VS2003
'Tools->Build Comment Web Pages ' would have been perfect. Oh well,
now I have to muddle through a bunch of malarky just to get a 1-page
document. It would be faster to edit as an HTML text file except
that I want it to be automatically updatable from the source.

Tried NDoc but I couldn't make it accept my project.

On Sun, 5 Mar 2006 10:43:47 -0500, "Kevin Spencer"
<ke***@DIESPAMMERSDIEtakempis.com> wrote:
Actually, I used the XSLT Editor and debugging tools in Visual Studio.Net.
But yes, that was about it.

So... where is the 'XSLT Editor'? I couldn't find it. Is it
basically the IDE with color tag highlighting and snippets?

How do you translate an XSLT file + XML doco into HTML? I couldn't
find the tool for this, either?

[ I'm sure a million other programmers will have to go through this.
Couldn't MS even supply a sample starting XSLT template?]

Does anyone know of a sample XSLT template from MS or something XSLT
open source?

Mar 14 '06 #28

P: n/a
On Tue, 14 Mar 2006 07:19:26 -0500, "Kevin Spencer"
<ke***@DIESPAMMERSDIEtakempis.com> wrote:
When you open an XSL
document in Visual Studio, it is opened in the XSL Editor, even though it
looks much the same as any other type of code file.


Thanks, that clears it up a bit.
Mar 14 '06 #29

P: n/a
GTi

Christoph Nahr wrote:
On 13 Mar 2006 14:53:30 -0800, "GTi" <tu****@gmail.com> wrote:
I have tested and used the nDoc with Whidbey C# support.
http://ndoc.sourceforge.net/wiki/dotNet_2.0_Support
And it works just fine - some compilling errors but I just ignore them.
It give me a nice MSDN look source doc.


When did you access that site? I just got this message:

"Could not get visitors lock: Check whether the web server can create
the directory /tmp/persistent/ndoc/wiki/temp and whether it can create
files in it."
--
http://www.kynosarges.de


Nope - That link is not working at all.
Anyway - Download the latest source
http://ndoc.sourceforge.net/ndoc-nightly.zip
And build it with VS 2005.
Exactly what I was looking for.

Mar 17 '06 #30

P: n/a
How is it working for you? Are you using VS2003 and creating help files
for VS2005? That's all the new version does.

Unless I am unaware of some setting changes to get the code to run
differently, there is no importing and documenting support for VS2005 in
NDoc 1.3.1 (including the Jonas version 1.3.1 v16). In other words, it
WILL NOT read a VS 2005 solution and output help files based on the
VS2005 solution and project files.

I stepped through both verion of NDoc's source code and the parser
immediately fails because it doesn;t recognize the newer C# project
files (the parsing works perfectly on VS2003).
I wish people would explain how they got it to work (step-by-step) or
stop tellling people that something is working that is NOT.

*** Sent via Developersdex http://www.developersdex.com ***
Apr 4 '06 #31

P: n/a
What version are you using? I downloaded the version of NDoc from the
nightly build and the version (full project) from Jonas.

I stepped through the program and none of the parsing is updated to .Net
2.0 files. It appears that the updating is for VS2003 solutions to be
capable of "OUTPUTTING" to .NET 2.0.(e.g. the help files will load in VS
2005) NDoc 1.3.1 v16 will not read and parse VS 2005 solution files and
create documents from them.
*** Sent via Developersdex http://www.developersdex.com ***
Apr 4 '06 #32

P: n/a


Except this is what keeps happening: # programmers want to program in C#
NOT XLST, and XML, and HTML, JavaScript...blah... blah...blah...
This "direction" you refer to is "crap". Look at the syntaxes a "good"
developer has to learn. If you make me laugh by talking about how
responsibilities could be divided between different peope, then I am
going to tell you thats how we got here i the forst place... tooo many
peple got "on their own" within their slice of the pie and transformed
their area into a separate language.

This constant division of and further subdivision is REDICULOUS! Plus,
why do I EVER need to transform documents if they were created in the
proper format in the first place?

You see, I have NO NEED for the xml output - in fact, NOBODY does.
Instead people are patting themselves on the back with how good a job
they did putting comments in an XML file that can be read universally.
Its so helpful that I have to add another "tool" to convert it to a
useable output.

Of course, your XLST may get you by, but I bet its is not an MSDN help
file that integrates with Visual Studio: it could but why should I as a
developer constantly have to "pay" to nbe "compatible" with what should
be simple and easily incorporated into the product.

WTF!

EVERY developer using VS2005 wants the summary tags output directly to
help files and they want the choice of separate cfm and/ or MSDN style
which integrates with VS Studio. They want control over the output and
they don;t want to pay third=parties just create files compatible with
Microsoft.
Microsoft failed miserably on this one and the lead should be fired
immediately for producing crap.

Trevor

*** Sent via Developersdex http://www.developersdex.com ***
Apr 4 '06 #33

P: n/a
GTi
1)
Download the source from:
http://ndoc.sourceforge.net/ndoc-nightly.zip

2)
Start MS Visual Studio 2005

3)
Open NDoc.sln and complete the Conversion Wizard

4)
Press F5 (Start debugging)

5)
Press Yes in the build error popup screen

6)
Press Add on the right side in the Ndoc application.
Locate your file(s) - for me it was a DLL file (C# .NET 2.0).

7)
Select documentation type MSDN

8)
Build documentation (Ctrl+Shift+B)

And there you a fine MSDN documentation of your source

Apr 4 '06 #34

P: n/a
GTi
PS!
It says SdkDocVersion is .Net Version 1.1 but it works fine anyway.
GTi wrote:
1)
Download the source from:
http://ndoc.sourceforge.net/ndoc-nightly.zip

2)
Start MS Visual Studio 2005

3)
Open NDoc.sln and complete the Conversion Wizard

4)
Press F5 (Start debugging)

5)
Press Yes in the build error popup screen

6)
Press Add on the right side in the Ndoc application.
Locate your file(s) - for me it was a DLL file (C# .NET 2.0).

7)
Select documentation type MSDN

8)
Build documentation (Ctrl+Shift+B)

And there you a fine MSDN documentation of your source


Apr 4 '06 #35

P: n/a
Dude, you need to get back on your meds.

--
HTH,

Kevin Spencer
Microsoft MVP
Professional Numbskull

Show me your certification without works,
and I'll show my certification
*by* my works.

"Trevor Westerdahl" <tr*****@artnirvana.com> wrote in message
news:uL**************@TK2MSFTNGP14.phx.gbl...


Except this is what keeps happening: # programmers want to program in C#
NOT XLST, and XML, and HTML, JavaScript...blah... blah...blah...
This "direction" you refer to is "crap". Look at the syntaxes a "good"
developer has to learn. If you make me laugh by talking about how
responsibilities could be divided between different peope, then I am
going to tell you thats how we got here i the forst place... tooo many
peple got "on their own" within their slice of the pie and transformed
their area into a separate language.

This constant division of and further subdivision is REDICULOUS! Plus,
why do I EVER need to transform documents if they were created in the
proper format in the first place?

You see, I have NO NEED for the xml output - in fact, NOBODY does.
Instead people are patting themselves on the back with how good a job
they did putting comments in an XML file that can be read universally.
Its so helpful that I have to add another "tool" to convert it to a
useable output.

Of course, your XLST may get you by, but I bet its is not an MSDN help
file that integrates with Visual Studio: it could but why should I as a
developer constantly have to "pay" to nbe "compatible" with what should
be simple and easily incorporated into the product.

WTF!

EVERY developer using VS2005 wants the summary tags output directly to
help files and they want the choice of separate cfm and/ or MSDN style
which integrates with VS Studio. They want control over the output and
they don;t want to pay third=parties just create files compatible with
Microsoft.
Microsoft failed miserably on this one and the lead should be fired
immediately for producing crap.

Trevor

*** Sent via Developersdex http://www.developersdex.com ***

Apr 4 '06 #36

P: n/a
I've come across this thread. I have a similar issue, I wish to
integrate my help files into a Visual Studio .Net project or solution.
The Projects will only have references to the .DLLs and maybe also the
XML files generated by VS from my code comments.
The help files I have are generated using the NDoc tool mentioned in an
earlier message.

Preferrably I would like to be able to select a keyword (e.g. Class
name) in a Source Code and hit F1, this would bring me to windows help
for that particular keyword, the same to what VS does for you right now
but for my own Code.

Can anyone help?

*** Sent via Developersdex http://www.developersdex.com ***
Apr 4 '06 #37

P: n/a
GTi
learnerplates wrote:
I've come across this thread. I have a similar issue, I wish to
integrate my help files into a Visual Studio .Net project or solution.
The Projects will only have references to the .DLLs and maybe also the
XML files generated by VS from my code comments.
The help files I have are generated using the NDoc tool mentioned in an
earlier message.

Preferrably I would like to be able to select a keyword (e.g. Class
name) in a Source Code and hit F1, this would bring me to windows help
for that particular keyword, the same to what VS does for you right now
but for my own Code.

Can anyone help?

*** Sent via Developersdex http://www.developersdex.com ***


http://ndoc.sourceforge.net/content/support.htm

Apr 4 '06 #38

P: n/a
Hello,
If I do it the way you described, following exceptions occur:

An error occured while trying to build the documentation.

Exception: NDoc.Core.DocumenterException
Unable to find the HTML Help Compiler. Please verify that the HTML Help
Workshop has been installed.

Exception: NDoc.Core.DocumenterException
Unable to find the HTML Help Compiler. Please verify that the HTML Help
Workshop has been installed.
Exception: NDoc.Core.DocumenterException
bei NDoc.Documenter.Msdn.MsdnDocumenter.Build(Project project) in
C:\Dokumente und
Einstellungen\tkraus\Desktop\ndoc\src\Documenter\M sdn\MsdnDocumenter.cs:Zeile
464.

bei NDoc.Gui.BuildWorker.ThreadProc() in C:\Dokumente und
Einstellungen\tkraus\Desktop\ndoc\src\Gui\BuildWor ker.cs:Zeile 63.

Exception: NDoc.Core.DocumenterException
bei NDoc.Documenter.Msdn.HtmlHelp.get_HtmlHelpCompiler () in
C:\Dokumente und
Einstellungen\tkraus\Desktop\ndoc\src\Documenter\M sdn\HtmlHelp.cs:Zeile 188.

bei NDoc.Documenter.Msdn.HtmlHelp.CompileProject() in C:\Dokumente
und
Einstellungen\tkraus\Desktop\ndoc\src\Documenter\M sdn\HtmlHelp.cs:Zeile 492.

bei NDoc.Documenter.Msdn.MsdnDocumenter.Build(Project project) in
C:\Dokumente und
Einstellungen\tkraus\Desktop\ndoc\src\Documenter\M sdn\MsdnDocumenter.cs:Zeile
435.

Bye
Thomas
GTi schrieb:
1)
Download the source from:
http://ndoc.sourceforge.net/ndoc-nightly.zip

2)
Start MS Visual Studio 2005

3)
Open NDoc.sln and complete the Conversion Wizard

4)
Press F5 (Start debugging)

5)
Press Yes in the build error popup screen

6)
Press Add on the right side in the Ndoc application.
Locate your file(s) - for me it was a DLL file (C# .NET 2.0).

7)
Select documentation type MSDN

8)
Build documentation (Ctrl+Shift+B)

And there you a fine MSDN documentation of your source

May 16 '06 #39

P: n/a
You need to install the html help workshop stuff. I believe it's
included in the windows sdk. It says int he NDoc wiki what is needed,
but that is currently down.

-Josh
Thomas Klein wrote:
Hello,
If I do it the way you described, following exceptions occur:

An error occured while trying to build the documentation.

Exception: NDoc.Core.DocumenterException
Unable to find the HTML Help Compiler. Please verify that the HTML Help
Workshop has been installed.

Exception: NDoc.Core.DocumenterException
Unable to find the HTML Help Compiler. Please verify that the HTML Help
Workshop has been installed.
Exception: NDoc.Core.DocumenterException
bei NDoc.Documenter.Msdn.MsdnDocumenter.Build(Project project) in
C:\Dokumente und
Einstellungen\tkraus\Desktop\ndoc\src\Documenter\M sdn\MsdnDocumenter.cs:Zeile
464.

bei NDoc.Gui.BuildWorker.ThreadProc() in C:\Dokumente und
Einstellungen\tkraus\Desktop\ndoc\src\Gui\BuildWor ker.cs:Zeile 63.

Exception: NDoc.Core.DocumenterException
bei NDoc.Documenter.Msdn.HtmlHelp.get_HtmlHelpCompiler () in
C:\Dokumente und
Einstellungen\tkraus\Desktop\ndoc\src\Documenter\M sdn\HtmlHelp.cs:Zeile 188.

bei NDoc.Documenter.Msdn.HtmlHelp.CompileProject() in C:\Dokumente
und
Einstellungen\tkraus\Desktop\ndoc\src\Documenter\M sdn\HtmlHelp.cs:Zeile 492.

bei NDoc.Documenter.Msdn.MsdnDocumenter.Build(Project project) in
C:\Dokumente und
Einstellungen\tkraus\Desktop\ndoc\src\Documenter\M sdn\MsdnDocumenter.cs:Zeile
435.

Bye
Thomas
GTi schrieb:
1)
Download the source from:
http://ndoc.sourceforge.net/ndoc-nightly.zip

2)
Start MS Visual Studio 2005

3)
Open NDoc.sln and complete the Conversion Wizard

4)
Press F5 (Start debugging)

5)
Press Yes in the build error popup screen

6)
Press Add on the right side in the Ndoc application.
Locate your file(s) - for me it was a DLL file (C# .NET 2.0).

7)
Select documentation type MSDN

8)
Build documentation (Ctrl+Shift+B)

And there you a fine MSDN documentation of your source


Jun 2 '06 #40

P: n/a
Actually, I think it's the visual studio help integration tool kit.

http://www.microsoft.com/downloads/d...DisplayLang=en

Narshe wrote:
You need to install the html help workshop stuff. I believe it's
included in the windows sdk. It says int he NDoc wiki what is needed,
but that is currently down.

-Josh
Thomas Klein wrote:
Hello,
If I do it the way you described, following exceptions occur:

An error occured while trying to build the documentation.

Exception: NDoc.Core.DocumenterException
Unable to find the HTML Help Compiler. Please verify that the HTML Help
Workshop has been installed.

Exception: NDoc.Core.DocumenterException
Unable to find the HTML Help Compiler. Please verify that the HTML Help
Workshop has been installed.
Exception: NDoc.Core.DocumenterException
bei NDoc.Documenter.Msdn.MsdnDocumenter.Build(Project project) in
C:\Dokumente und
Einstellungen\tkraus\Desktop\ndoc\src\Documenter\M sdn\MsdnDocumenter.cs:Zeile
464.

bei NDoc.Gui.BuildWorker.ThreadProc() in C:\Dokumente und
Einstellungen\tkraus\Desktop\ndoc\src\Gui\BuildWor ker.cs:Zeile 63.

Exception: NDoc.Core.DocumenterException
bei NDoc.Documenter.Msdn.HtmlHelp.get_HtmlHelpCompiler () in
C:\Dokumente und
Einstellungen\tkraus\Desktop\ndoc\src\Documenter\M sdn\HtmlHelp.cs:Zeile 188.

bei NDoc.Documenter.Msdn.HtmlHelp.CompileProject() in C:\Dokumente
und
Einstellungen\tkraus\Desktop\ndoc\src\Documenter\M sdn\HtmlHelp.cs:Zeile 492.

bei NDoc.Documenter.Msdn.MsdnDocumenter.Build(Project project) in
C:\Dokumente und
Einstellungen\tkraus\Desktop\ndoc\src\Documenter\M sdn\MsdnDocumenter.cs:Zeile
435.

Bye
Thomas
GTi schrieb:
1)
Download the source from:
http://ndoc.sourceforge.net/ndoc-nightly.zip

2)
Start MS Visual Studio 2005

3)
Open NDoc.sln and complete the Conversion Wizard

4)
Press F5 (Start debugging)

5)
Press Yes in the build error popup screen

6)
Press Add on the right side in the Ndoc application.
Locate your file(s) - for me it was a DLL file (C# .NET 2.0).

7)
Select documentation type MSDN

8)
Build documentation (Ctrl+Shift+B)

And there you a fine MSDN documentation of your source


Jun 2 '06 #41

This discussion thread is closed

Replies have been disabled for this discussion.