G'day from Australia!
I've head great things about GhostDoc and I'm just now starting to us it within my own code. I have utilized XMLDoc extensivily throughout my codebase and I was hoping that GhostDoc would help automate some of the management I must preform in order to keep all of the XMLDocs properly synced and up-to-date. I am as consistent as possible in my function, property and argument names (i.e. Class.Reset, Class.Data, etc.) and currently I have to manually copy and paste throughout the codebase in order to keep similar functions/properties/arguments described consistently.
One feature I was surprised was not there in GhostDoc (or at least that I've not found yet) is the ability to base new XMLDoc entries on previous entries from the same file/project/solution. For example, I just documented a class with 6 interfaces that differ only in argument ordering and types using GhostDoc:
///<summary>
///Maps data between the provided objects.
///</summary>
///<param name="oFrom">Object to be used as the source.</param>
///<param name="oTo">Object to be used as the destination.</param>
///<returns>Boolean value representing if all properties within <paramref name="oTo" /> were populated.</returns>
public static bool Map(BusinessObject oFrom, object oTo) {...}
[Document this]
public static bool Map(object oFrom, BusinessObject oTo) {...}
I would find it VERY useful if GhostDoc, when asked to "Document this" on the second function would use the data from the other XMLDoc as a basis to for the new documentation.
Other examples from my code include arguments with names like "string sTableName", "string sColumnName", "SettingsObject oSettings". These arguments always have the exact same description throughout my code, so it would be nice if GhostDoc would query the current XMLDoc entries and if a match is found use that as the entry for the new XMLDoc.
Anyway... thank you for your work to date on GhostDoc. It would have been extremely useful as is in the early days of my codebase, but less so now that I'm attempting to maintain consistency based on the previously established descriptions (but hopefully I've merely overlooked this feature ;).
Nick