SQL Documentation Tool 7.6 for SQL Server

The SQL Documentation Tool is a complete documentation solution for Microsoft SQL Server databases. It automatically creates comprehensive technical documentation reports for databases, saving valuable developer time and money.

Reports are created in HTML [sample], Microsoft's HTML Help [sample], RTF [sample] and text [sample] formats. Color coded, syntax highlighted copies of the Transact SQL associated with stored procedures, functions and views are included with the reports. The compiled HTML Help reports includes an index and search facility.

Version 7.6 offers the following update:

• There is now an option to document dependency information for database tables, views, stored procedures and triggers. Note: Dependency information will not be shown for triggers unless database tables are documented. Documenting dependencies may significantly slow down the data extraction routines, particularly on very large databases.

Download SQL Documentation Tool Trial Version

.NET Documentation Tool 8.6 (C#/VB.NET)

The .NET Documentation Tool creates comprehensive technical software documentation for .NET Framework applications written in VB.NET or C#. Microsoft SQL Server and Microsoft Access databases associated with the application may also be documented if required. There is special functionality for documenting ASP.NET web applications. (Classic ASP version also available).

Reports are created in HTML [sample], Microsoft's HTML Help [sample] and text [sample] formats. Color coded, syntax highlighted copies of the .NET and SQL code are included with the reports. The compiled HTML Help reports include fully searchable source code, making the
.NET Documentation Tool an invaluable utility in understanding your (or someone
else's!) applications. Versions for ASP and Visual Basic 6.0 are also available.

Changes in version 8.6 of the .NET Documentation Tool are:

• If the .NET Documentation Tool is run using the graphical user interface, the console window now appears for longer if there is an error, making it easier to resolve the issue. Most errors are caused by the specified input or output folders not existing.


• The OutputDir option is no longer saved to the configuration file - the correct option is OutputFolder.


• The LogFileDir option is no longer saved to the configuration file as the option is not required.


• Saving the configuration file now shows the filename of the configuration file that is being overwritten.


• The installer has been changed.
  
  .NET Documentation Tool Trial Version