|
VSNETcodePrint 2003– Version History All Rights Reserved |
|||||||||
|
Version |
Description |
||||||||
|
7.2.18 |
Microsoft
Windows Vista support added |
||||||||
|
7.2.17 |
Fixed Bugs:
|
||||||||
|
7.2.16 |
Fixed Bugs: If connecting lines carried
over a page exceed 9 then the numbering of lines 10 onwards is not printed
correctly. |
||||||||
|
7.2.15 |
Fixed Bugs: On rare occasions a
registered version of the addin become the trial version. |
||||||||
|
7.2.14 |
Fixed Bugs: ·
A
comment in C# and J# as shown below is not output as a comment: strSaveName = strPath + "\\" + /* <------------ */ ·
A
extra character ‘\’ to be output at the end of C# and J# multi-line comments: ·
TABs
in the source code are not handled correctly ·
Error
occurs if [Declarations for ProjectItem] is select from the Custom Selection
window ·
‘Format
Source Code’ option is not remembered between VS.NET IDE reloads ·
Sometimes
the following error is reported when previewing a C# project item: Message: Item has already been added. Key in dictionary:
'82' Stage: at
VSNETcodePrint2003.clsCodeProcessor.getOutlines(Document doc) |
||||||||
|
7.2.13 |
Fixed Bugs: ·
Export
truncates after 3 pages |
||||||||
|
7.2.12 |
Fixed Bugs: ·
If Keep Procedure lines together option is selection from the
General options then the Add-in starts some procedures start on a new page
unnecessarily. ·
Printing
ASP.NET projects does not print more than 3 pages |
||||||||
|
7.2.11 |
Enhancements: ·
The Table Of Contents (TOC) now outputs the line number
as well as the page number where the item starts. It used to output just the
page number ·
The custom page header and
footer strings now support macro and environment variable substitution. Supported macros
are: {Datetime} {Date} {Page} {Project
Name} {Project
Short Filename} {Project
Long Filename} {ProjectItem
Name} {ProjectItem
Long Filename} {ProjectItem
Short Filename} {Solution
Name} {Time} Environment variable should be enclosed
in % characters. For example, %USERNAME% Examples: 1. Click on Options
on the VS.NETcodePrint menu 2. Click on Headers
& Footer node 3. Click on Header or Footer node 4. Enter a string that
contains one of the above macros or %environment variable% in the left,
centre or right segment for header and or footer as show below:
Fixed Bugs: ·
HTML code processing logic has been enhanced to improve
performance ·
Improved error handling ·
The option to reset line numbers does not work correctly |
||||||||
|
7.2.10 |
Fixed Bugs: ·
Export to PDF fails with error
System.NullReferenceException ·
Some files are added to the Index when they should not be
·
Excluding
files without their paths does not work. For example,
pattern aaa*.* does not exclude all files that start with 'aaa'
and any extension ·
Connecting
lines for statements that include : character inside a string are not drawn
correctly: Example: If szText =":DIR" Then
szText =""
·
ASP.NET
project items with ext .apcx are not processed ·
Code for
UserControls in a ASP.NET project is not processed ·
Not all
files are included in the Table of Contents ·
Source code
comment lines that split over multiple lines in XML or HTML are not treated as comments |
||||||||
|
7.2.8 |
Fixed Bugs: ·
Excluding
files without their paths does not work. For example,
pattern aaa*.* does not exclude all files that start with 'aaa'
and any extension ·
Connecting
lines for statements that include : character inside a string are not drawn
correctly: Example: If szText =":DIR" Then
szText =""
·
ASP.NET
project items with ext .apcx are not processed ·
Code for
UserControls in a ASP.NET project is not processed ·
Not all
files are included in the Table of Contents ·
Source code
comment lines that split over multiple lines in XML or HTML are not treated as comments |
||||||||
|
7.2.7 |
Fixed Bugs: ·
A
bug in Visual Studio 2003 IDE sometime caused the Addin to fail with Error:
'The parameter is invalid' at EnvDTE.CodeElement.get_EndPoint. |
||||||||
|
7.2.6 |
Fixed Bugs: ·
Connecting
lines are not drawn correctly for ‘If’ statements that do not end with ‘End
If’ as shown below: If Keyword= “” Then
keyword=”Default” Cancel button does not work on
‘Generating Index’ popup ·
The
Addin fails with Error: 'The parameter is invalid' at
EnvDTE.CodeElement.get_EndPoint ·
The
processing of Outlined source code is not available when processinga
Namespace, Class or Module. It is only available when the whole ProjectItem
is selected for processing ·
The registration code for CSharp is lost between Visual Studio IDE
reloads ·
Enhancements: ·
The
Indenting options for the language's text editorcan now be changed using the
VS.NETcodePrint Options dialog box (using the Formatting/Indenting tab). In
the previous version these option were ReadOnly ·
Outlined
source code can now be handled in all versions of the Addin. Previously this
functionality was only available in the Developer Suite of the Addin |
||||||||
|
7.2.5 |
Fixed Bugs: ·
The
custom selection window does not show folders in the project ·
When
loading the Addin using devenv command then an error occurs in
the addin when creating the toolbar (Object reference on set in
EnvDTE._DTE_get_CommandBars() ) |
||||||||
|
7.2.4 |
Fixed Bugs: ·
Selecting
Print, Preview or Export from the addin’s toolbar does not always output the
item showing in the ‘Print What’ dropdown list ·
Selecting
Print, Preview or Export from the Custom Selection window does not always
output all the selected items |
||||||||
|
7.2.3 |
Fixed Bugs: ·
Connecting
lines are drawn correctly when functions/properties are decorated with
attributes on the same line like: <Editor(GetType(FileNameEditor))> Public Readonly
Property ·
Registration
codes are accepts for version 7.1 that was upgraded from VBcodePrint |
||||||||
|
7.2.2 |
Fixed Bugs: ·
The registration codes do not stick between reloads of
the IDE |
||||||||
|
7.2.1 |
Fixed Bugs: ·
Option ‘Output code in closed Outlines’ is not remembered
between IDE session ·
Avoid error if the add-in is not able to get the fonts and
colors from the IDE ·
Fix the bug that causes a procedure/function/property source
code to split over a page boundary when the option ‘Keep procedure lines
together’ is set in the General options ·
The valid upgrade registration codes are not accepted |
||||||||
|
7.2.0 |
Enhancements: Print
ASP.NET Source Code ·
The source behind ASP.NET web page can be output ·
The style sheets can be output ·
The HTML source code be output ·
The XML files can be
output Outlines
Processing This option is only available when you
purchase Developer Suite license ·
Implemented functionality to omit source code printing in closed/collapsed Outlines ·
The Outlines markers are printed in the source code Fixed Bugs: ·
If there are comments before the procedure, class, module,
namespace headers then the divider line is drawn before the header comments ·
Cancel button does not cancel a long print/preview/export
action ·
C# and J#: Connecting lines are not drawn correctly if characters ‘{‘ and
‘}’ appear on the same line of source code. For example: } else { ·
C# and J#: Connecting lines are not drawn for construct like using {…} ·
C# and J#: Characters ‘{’ or ‘}’ in a string cause confusion for the
connecting lines logic ·
Program error occurs if
preview window is closed while the preview is in progress |
||||||||