spaccabit

A questo indirizzo è disponibile la nuova versione di GhostDoc. Per chi non lo conoscesse GhostDoc è un add-In per VS.NET che facilita la creazione della documentazione per i nostri sorgenti.

Qui di seguito riporto le nuove feature e fix della  versione 2.0 :

• Added: Support for Visual Studio codename "Orcas". Note that GhostDoc for Visual Studio 2005 and GhostDoc for Visual Studio "Orcas" are released in separate setups and have to be installed into separate folders. Both offer equal functionality and thus share the same configuration file, though. This will stay this way as long as GhostDoc 2.x is released both for 2005 and "Orcas".
• Added: Support for generic methods. The type parameters are now documented using the <typeparam> tag. For type parameter names starting with 'T' (e.g. "TKey") documentation text is generated (e.g. "Type of the key"), for all other type parameter names the text is left empty. Note that this behavior is currently hard-coded.
• Added: New text generation rules for classes, interfaces and structs (with support for generic type parameters). The default rules generate empty summaries and place the cursor so you can start typing the summary immediately. It is possible to change the summary template to insert e.g. the class name split into individual words, but honestly I don't want to ship GhostDoc with that behavior by default as I didn't find it too helpful. In addition to the default rules, it's also possible to define custom rules (e.g. for classes with a name ending on a specific suffix).
• Added: A new macro $(End) for specifying the location of the text cursor after the documentation text has been generated.
• Added: A new macro $(Rule) that inserts the display name of the rule that generated for documentation text. Useful for debugging custom rules, this macro can e.g. be used in the custom text that is added to new doc comments (see the last tab of the GhostDoc configuration dialog).
• Added: A macro of the format $(%VarName%) inserts the value of the environment variable with the name "VarName" (or an empty string if no variable with that name exists).
• Added: A few language elements are now supported with limited functionality, i.e. without specific rule types (new rule types may be added in future versions, but they didn't have a high priority to be included in 2.0 as the existing functionality already helps a lot):
  • enums - empty summaries for the enum and all of its values
  • enum values - empty summary
  • events - summary starting with "Occurs when"
  • delegates - empty summary
  • variables - empty summary
  The cursor is moved inside the summary tag so you can start typing right away. As usual, existing documentation will not be overridden.
• Added: New method rules:
  • A rule for Dispose(bool disposing)
  • A rule for overloaded operators
  • Rules for implicit/explicit conversion operators
  On a side note, these new rules have been implemented using custom method rules, i.e. using only what was already available in earlier versions of GhostDoc.
• Added: Before upgrading or importing a configuration, it is now possible to quickly create a backup copy by clicking the link in the lower left of the dialog. This is useful especially during an upgrade installation.
• Changed: The experimental support for VB.Net has been disabled in this release. I was pretty tight on my time budget and couldn't spend any time on keeping support for C# and VB.Net in sync.
• Changed: The demo project is no longer installed to a sub-folder of the GhostDoc directory (where it caused problems when working with a non-admin account). Instead, the demo project is now an optional feature with its own setup, suggesting an installation path in the user's Visual Studio project folder.
• Fixed: Error message when installing GhostDoc by double-clicking the MSI file on a Vista system.
• Fixed: When defining custom rules, conditions for method and type names didn't work well with type parameters (generics).
• Fixed: The "Document this" command worked only when the cursor was positioned in a specific way. This has been relaxed, the cursor may now also be positioned on the whitespace before the language element (in the same line as the identifier), or somewhere inside the documentation comment.

Powered by ScribeFire.