Recommended documentation add-on for Visual Studio 2010: GhostDoc

, posted: 12-Dec-2011 16:00

During my six years of commercial development experience I have stumbled upon different kinds of add-ons that developers can use to integrate into the Visual Studio environment and get extra functionality that was missing.

Generally these tools make it for a better experience for the developer, saving both time and effort in long projects. GhostDoc is one I've been using especially in Visual Studio 2010 to help with documentation, so I decided to write a brief blog post on how it works and what it does.

GhostDoc comes in two different versions (free or paid) and works with both C# and VB.Net.

I've been using the free version, which accomplishes exactly what I need it to do. Once it is installed browse to your class/code that you have created:



Right click on the section you wish to create comments on, which could be the Class, Variable or Sub/Function declaration - and Click "Document This!":



GhostDoc will auto generate comments on each section, and on Sub/Functions will try to guess what the function is used for, along with what Parameters are expected.

It is a basic add-on, but I have found that even the simple add-ons add extra value.

Documentation is a normal practice used in the Industry, so this add-in will definitely help you with this. It integrates perfectly in the Visual Studio IDE.

Download a trial of Visual Studio 2010.

About the author

Stephen Aitchison is senior developer at Aura Redeye Security Ltd. You can find him on Twitter as @NZCoderGuy and on Geekzone as well.

Other related posts:
NuGet Package Manager extension for Visual Studio 2010
Getting Started with Visual Studio LightSwitch 2011








Comment by Daniel Ballinger, on 13-Dec-2011 10:22

Personally I don't find much value from a tool like GhostDoc if the generated documentation stubs are left as is. You don't get any information that couldn't otherwise be inferred from the code itself. Adding some additional information beyond the method and parameter names will help other developers who are using the code. E.g. Is there a limit on the length of the name field? Can it be null? In what cases will an exception occur.


Add a comment

Please note: comments that are inappropriate or promotional in nature will be deleted. E-mail addresses are not displayed, but you must enter a valid e-mail address to confirm your comments.

Are you a registered Geekzone user? Login to have the fields below automatically filled in for you and to enable links in comments. If you have (or qualify to have) a Geekzone Blog then your comment will be automatically confirmed and shown in this blog post.

Your name:

Your e-mail:

Your webpage:

About the Visual Studio blog

In the years since the hugely successful release of Visual Studio 2005, Microsoft has used developer feedback from all over the world to introduce new features in later releases.

This sponsored blog will bring Visual Studio tips and tricks from well known developers in the New Zealand tech community directly to you.

Every second day during November and December 2011 you will find something new here. Make sure you bookmark this blog or subscribe to its RSS feed.    

Join us on Twitter

Find us on Facebook

Tags

Blog...
Database...
Techniques...
Testing...
Tools...
User Interface...
Windows Phone...


Other blog posts

Winners of Windows Phone compe...
Customise your Visual Studio 2...
Secure Development Tips and Te...
NuGet Package Manager extensio...
Competition: be in to win one ...
Consuming JSON web APIs with V...
Test driven development in Vis...
Web.config transforms...
Getting Started with Visual St...
Welcome to the Visual Studio b...


Recent comments

kiwiandy on Winners of Windows Phone competition announced, mo: mm the first one I try... ASB.. isnt there!?...

chiefie on Winners of Windows Phone competition announced, mo: Hmm the ASB Bank app is MIA....

Daniel Ballinger on Recommended documentation add-on for Visual Studio: Personally I don't find much value from a tool like GhostDoc if the generated do...



Disclaimer

The Visual Studio blog is sponsored by Microsoft NZ. The blog posts are the authors' genuine accounts of their experiences with Visual Studio, Windows Phone SDK and Windows Azure Platform and are not influenced or filtered by Microsoft New Zealand in any way.