Download Latest
My Contact Info
Change Password
License Status
Fetch License
Return License
Product News
Maintenance Policy
FAQs
Download SDK
Contact Us
  HomeSupport
11/16/02 - DocJet version 5.0 build 3 released
This release introduces support for documenting Active Server Pages and VBScript.

New Features

  • You can now document functions found in Active Server Pages and VBScript files.
  • IDL Cleanup Hook can be used for interfaces defined in C++.

Defects Corrected

  • If you opened a corrupted .DOF file with the output format editor, it would throw an unhandled exception.
  • The JavaScript scanner did not report variables. In most cases, users didn't want to document the variables anyway, but a few did. If you don't want to deal with the variables, you can Automatic Comments to get rid of them.
  • If the C++ scanner encountered an error within a namespace{} block, it wouldn't terminate the scan, leading to other syntax errors and, in a few circumstances, a GPF.
  • When the C++ scanner encounters a syntax error within a class, it now reports the class, where it didn't before. Without reporting the class, you get a syntax error plus a whole bunch of "missing class definition" errors, which obscured the real error.
  • The C++ scanner did not recognize __property as a MC++ extension
  • The list of variables on the "Variables" page of the project configuration wasn't sorted. What a pain.
  • The links in the class members list didn't have hover-over capability.
  • The "Make All Classes Public" flag in the VB6 scanner didn't do anything for modules.
  • The Directory/File Grouper Hook could infinite loop if you used "//" comments as the comment for a file.
  • The leading-character unboxer was not working for VB6 comments that started with a string of ticks.
  • The VB scanner was not reporting properties correctly. (The generator would report duplicate object errors.)
  • The MSWord output format did not handle papers from DJX files
  • The XML Comment Scanner did not translate <PARAM> correctly.
  • Way back in the day, the "Description" section of a comment absolutely had to be one paragraph and no more. The last vestiges of that restriction have now been erased.
Enter your customer ID and optional password below to gain access to your license status information.
Customer ID:
Password: