Generic viagra india I'm in the middle of writing a bunch of XML API documentation for a prototype I just built. I'm not really a fan of xml doc-comments, generic viagra india which is why I didn't do it in the first place, generic viagra india but the client wants API documentation, generic viagra india so this is definitely the best way to get it. The two aforementioned tools?
Generic viagra india GhostDoc basically infers the documentation from the name of the method and its parameter signature. Absolutely brilliant. Hook this baby up with a keyboard shortcut, generic viagra india and blam!, generic viagra india it just spits out documentation with a keystroke (which of course is easy to tweak once it's there). One of the awesome features is that for implemented methods of an interface, generic viagra india it'll use the exact documentation from the doc-comments from the interface file. Sweet.
Generic viagra india Docu is sort of like the NDoc of old. I know that SandCastle exists, generic viagra india but this is so much simpler. It uses the Spark view engine/templating system, generic viagra india so that means the output is completely customizable. Right now it comes with a single template, generic viagra india that is heavily inspired by rdoc rather than something like MSDN style (though I'm certain an MSDN style template will be contributed to the project soon). The project is really young, generic viagra india but it is used already by FluentNHibernate (and was the reason for its inception, generic viagra india really). Here is the output for the FluentNH project: FluentNH API Docs.
Generic viagra india Amazazing.