VB.NET Documentation Tool 7.1

VB.NET Documentation Tool 7.1 offers you a great tool that can allow you to create comprehensive documentation for .NET Framework projects developed in VB.NET and their associated SQL Server/Microsoft Access databases. Most types of project (Windows Forms, ASP.NET, etc.) are supported. Reports are created in standard HTML, Microsoft HTML Help and plain text formats. Silverlight/WPF supported. Includes documentation, Premium Edition contains source code. An ASP and Visual Basic 6.0 Documentation Tool are also available - there are discounts when purchased together with the VB.NET Documentation Tool.

Major features

1. Supports the following project types:
   
   • ASP.NET
   • Windows Forms
   • Console Applications
   • Class libraries
2. More than one project can included in the documentation, making it possible to document entire Visual Studio "Solutions".
   
3. • For ASP.NET projects, the file parser extracts content from files written in either VB.NET or C#. Supported file types are:
   • ASP.NET files (.aspx, .asax).
   • User Controls (.ascx).
   • Master pages (.master).
   • Web Services (.asmx).
   • HTTP Handlers/Web Handlers (.ashx).
   • Code Behind Files containing the code associated with ASP.NET files and User Controls.
   • Custom components (.vb and .cs).
   • Web.config files.
   • Cascading Style Sheet (CSS) files.
   • ASP.NET 2.0 site map files.
4. For Windows Forms projects and other non-ASP.NET projects, the file parser extracts content from files written in either VB.NET or C#. Supported file types are:
   
   • Windows Forms (.vb, .cs).
   • Custom components/classes (.vb and .cs).
   • App.config files.
5. Supports most C# and VB.NET XML Comments used by Visual Studio.NET and other code editors.
   
6. Compatible with .NET Framework 1.0, 1.1, 2.0, 3.0 and 3.5 code.
7. Silverlight/WPF files are also supported. Note that this technology is still in the early stages of development by Microsoft and may be subject to change.
   
8. Configuration of the .NET Documentation Tool is through the editing of a plain text configuration file
   Can be scheduled to automatically update project documentation by making use of the Windows AT command or the Task Scheduler.
   
9. Can be integrated with Visual Studio.NET through the Tools menu bar.
   
10. Detailed product documentation in Microsoft's HTML Help format.
    
11. Log file creation shows a comprehensive summary of the .NET Documentation Tool's actions.
    
12. Report shows the following for both VB.NET and C#:
    
    • Namespaces: What namespaces are in the project, and which classes are in each namespace.
    • Classes: What classes are in the project, which namespace they belong to and what constructors, functions and subroutines are defined within each class. Partial classes are also supported.
    • Enumerators and their properties.
    • Properties.
    • Constructors: Where they are defined, and which arguments they use.
    • Functions: Where they are defined, and which arguments they use.
    • Subroutines: Where they are defined, and which arguments they use.
13. Additionally for ASP.NET projects:
    
    • Where Application and Session variables are used.
    • Which User Controls are used in the project.
    • Which Web Controls are used in the project.
    • Which Validation Controls are used in the project.
    • What web.config files are used on the project.
14. For Windows projects:
    
    • What app.config files are used on the project.
    • What controls are used on Windows Forms.
    • Where email addresses are located in the project.
15. SQL Server 7.0, 2000 and 2005 databases associated with the .NET project can also be documented, with the following features:

• Shows a list of tables within the database.
• Shows a list of views within the database.
• Shows a list of column names, type and length associated with each table.
• Shows a list of stored procedures, including the full text of each stored procedure and its input parameters.
• Shows where the stored procedure is called from in code (provided the EXEC keyword is used in SQL statements or the stored procedures are prefixed with "sp_").

Requirements: Uses Microsofts HTML Help Workshop (if installed)

WareSeeker Editor