I'm not exactly sure what type of documentation you're talking about, but using the /doc switch in compilation seems to make a fairly comprehensive documentation in vs.net beta 2
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I am fully aware of the switch. But there are few things to be considered:
1: /doc:<op-file> generates a SINGLE file
1.x: I want a whole lot of directory structure just as it is with javadoc.
2: the compiler currently understands only the language of MS:xml stylo comments.
2.x: I am estimating that initially most of the applications / libraries build for dotNET would be ports from java, I want to keep the java-stylo tags support also.
Java tags are cheaper than xml tags!
3.x: The application will also generate other required files, like namespace.html, index.html (@@), help.html etc alongwith a default styles.css if none provided.
4.x: The programmer / doc-writer is saved from a lot of hassles, esp if the application is ported - cut/copy/paste comments from the java source.
Cheers,
Master Gaurav
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm not exactly sure what type of documentation you're talking about, but using the /doc switch in compilation seems to make a fairly comprehensive documentation in vs.net beta 2
Hi,
I am fully aware of the switch. But there are few things to be considered:
1: /doc:<op-file> generates a SINGLE file
1.x: I want a whole lot of directory structure just as it is with javadoc.
2: the compiler currently understands only the language of MS:xml stylo comments.
2.x: I am estimating that initially most of the applications / libraries build for dotNET would be ports from java, I want to keep the java-stylo tags support also.
Java tags are cheaper than xml tags!
3.x: The application will also generate other required files, like namespace.html, index.html (@@), help.html etc alongwith a default styles.css if none provided.
4.x: The programmer / doc-writer is saved from a lot of hassles, esp if the application is ported - cut/copy/paste comments from the java source.
Cheers,
Master Gaurav