|
VSNETcodePrint 2005 – Version History All Rights Reserved |
|||||||||||
|
Version |
Description |
||||||||||
|
9.0.7 |
Fixed Bugs: ü Lines numbers
sometimes are not output correctly ü Table of Contents (TOC)
is not produced when source code is output using ‘Custom Selection’. ü Paper Size and Page orientation is not remembered between
reloads of VSNETcodePrint |
||||||||||
|
9.0.6 |
Enhancements: ü The output is
generated in memory and may cause ‘out of memory’ exception when generating
output for very large solutions. The addin has been enhanced to consume less
memory. ü Font setting for Procedure Header, Namespace and Class and Module turned
out to be very confusing and therefore the option to set them has been
withdrawn ü Connecting lines in
the Preview of options were not correctly drawn ü If there is no
project loaded in the IDE or no ProjectItem open in the code window then the
Addin is not able to determine the language for the source code to be
displayed in the preview window. This version of the Addin allows the user to
select the language. |
||||||||||
|
9.0.1 |
Fixed Bugs: The
previous version insisted that .NET Framework version 3.5 was installed. This version relies on version .NET
Framework version 2. |
||||||||||
|
9.0.0 |
Enhancements: ü Supports 64-bit operating systems All previous versions of
VSNETcodePrint2008 used ComponentONE ActiveX control, vsView, for printing,
previewing and exporting. This ActiveX does not work on computers that have
hardware-enabled Data Execution protection (DEP) implemented.
VSNETcodePrint2005 version 8.0 fails with the following exception: Unable to get the window handle for the 'AxVSPrinter'
control. Windowless ActiveX controls are not supported. Source="System.Windows.Forms" ü The exported PDF
files: o
Can be secured using username and password o
Restricted from printing, copying and editing o
Can be annotated o
Shows contents with Outlines ü Produces much
improved exported output ü The Preview has an
‘Outline View’ that is very useful when navigating the output ü Performance has been
improved by a factor of 5 ü Page numbers in Table
of Contents and indices reference actual pages in the document rather than
the page numbers printed in the header/footer ü Exported can be
compressed and password protected and document information can be added ü The text in the
preview window can be searched ü Long lines are
wrapped correctly ü The page numbers in
the Table of Contents(TOC) are
represented by links to the appropriate page numbers ü The page numbers in the
Indices that are produced for each ProjectItem and project are links to the
corresponding page number ü The preview and
exported PDF has outline view that allows you to navigate to pages quickly ü The default directory
for exports is set to ‘My Documents’ ü The Table of contents
(TOC) is produced when previewing, printing or exporting a class, module,
Namespace or an ProjectItem ü The PDF file can be Fixed Bugs: ü
A number of minor bugs have been fixed ü
Output line numbers correctly when the option
is set to reset line numbers at the ‘start of each procedure’ ü
Print/Preview/Export for ‘Current
Procedure’, ‘Current Class’, ‘Current Module’ or ‘Current Namespace’ does not
always works for C# ü
Fixes the following program exceptions: 1.
Message: Object reference not set to an instance of an object. |
||||||||||
|
|
|
||||||||||
|
8.1.84 |
Fixed Bugs: ·
If a project in a Solution is
not loaded (i.e. Solution Explorer shows ProjectName
(unavailable) then the following exception will occur
when Table of Contents (TOC) is generated: Message: Object reference not set to an instance
of an object. |
||||||||||
|
|
|
||||||||||
|
8.1.83 |
Fixed Bugs: ·
Occasionally the following
exception occurs when Table of Contents is selected: Message: Unspecified error ·
The Preview window disappears behind the
VS2005 IDE window ·
Table of Contents(TOC) header does not
align correctly ·
Exceptions occur if an attempt is made to
print/preview items if a solution that contains a project that is not
supported by the Addin (InstallShield project) |
||||||||||
|
8.1.82 |
Fixed Bugs: ·
An exception occurs when exporting
project/solution details |
||||||||||
|
8.1.81 |
Fixed Bugs: ·
When printing a project or solution some
ProjectItems are output twice ·
Occasionally error exceptions occur when initializing
printer ·
When ‘Print/Export/Preview
CurrentProjectItem’ option is selected then the header/footer does not
substitute macros ( {ProjectItem Name}, {Project Name} etc) on the 1st
page of source code ·
User customizable Options are maintained in
a file placed in a folder to which the current user will always have
permissions to update ·
VSNETcodePrint 2005 Addin is installed for
“everyone” by default and the user preferences are maintained for every user
separately |
||||||||||
|
8.1.78 |
Support
for Microsoft Vista added |
||||||||||
|
8.1.76 |
Fixed Bugs: ·
Print Solution or Project details does not
recurse through nested folders in the project/solution ·
The option to reset line numbering to
‘Never’ does not work ·
Page numbers in the Table of Contents are
incorrect ·
The source code of items in a project is
not output if they are not open in the IDE Enhancements: ·
The source code line counts are shown for
each project item and as well as the totals in each project ·
The items specified using the ‘Exclude
files and folders’ option are not included in the details |
||||||||||
|
8.1.75 |
Fixed Bugs: ·
An error occurs if you change the ‘Number
of Columns’ value too quickly on the options form ·
Occasionally an error occurs if project
details are previewed or printed ·
Setting Duplex value on the Options form
does not take affect as expected ·
Fix the following error: |
||||||||||
|
8.1.74 |
Rebuilt
so that the install process automatically uninstalls the previous version. |
||||||||||
|
8.1.73 |
If an
attempt is made to print, preview or export a project that is not supported
by the Addin, a message is displayed. This message is now suppressed on
user’s request. |
||||||||||
|
8.1.72 |
Fixed Bugs: ·
Connecting lines are not numbered correctly
if the more that 9 of them are carried over to the next page |
||||||||||
|
8.1.71 |
Fixed Bugs: ·
The header and footers of the last page
before Index do not have correct values output ·
If bitmaps file are not excluded using the
excluded filter in the options then the image files are opened using the
default file editor for the image file ·
Program errors occurs when the locale is
not English 1.
Message: Failed
to compare two elements in the array. Stage: Stack:
at System.Array.BinarySearch(Array array, Int32 index, Int32 length,
Object value, IComparer comparer) 2.
Message: Item has
already been added. Key in dictionary:
'C:.Documents and Settings.Joginder.My Documents.Visual Studio
2005.WebSites.Test.textstyles cs' Key being added: 'C:.Documents and
Settings.Joginder.My Documents.Visual Studio 2005.WebSites.Test.textstyles cs' |
||||||||||
|
8.1.70 |
Fixed Bugs: ·
Program error occurs when the locale is not
English ·
Page margins get set to incorrect values if
the Addin is run in one locale and restarted in another one |
||||||||||
|
8.1.68 |
Fixed Bugs: ·
Version 8.1.67 introduced a bug such that WEB
projects were not recognized ·
Printing .XSD files inserted the following
code: Partial Class xxx End Class |
||||||||||
|
8.1.67 |
Fixed Bugs: ·
Program error occurs when printing Compact
Framework application that has SDF
file ·
XSD file and its associated files are not
always processed correctly ·
Custom selection windows does not display
the Solution correctly if there are Solution Folders in a solution ·
The following error is reported if you select
a single procedure to output from the Custom
Selection window: Message: Unable to cast object of type ‘NodeTag’
to type ‘EnvDTE.CodeElement’ ·
The following error is reported if a
solution contains solution folders: Message: key cannot be null ·
The following error is reported if you have
code files with the same name in different folders : Message: Item has already been added in
dictionary: … |
||||||||||
|
8.1.64 |
Fixed Bugs: ·
VS.NETcodePrint reports an error when the
Visual Studio is started ·
A Table of Contents (TOC) is sometimes
empty |
||||||||||
|
8.1.63 |
Fixed Bugs: ·
If the option is selected to output the source
code in multiple columns then the watermark is rendered within the column
width rather than the page width. This
is true when the watermark is rendered on an Index page (especially the last
page) ·
The Table of Contents (TOC) sometimes
contains an entry for a folder whose contents have been excluded from
printing using Exclude Files and
Folders option ·
If Settings.settings file
is included in the printout then after a print/preview of a project, any
attempts open Settings from
the Project Properties gives an error. |
||||||||||
|
8.1.62 |
Fixed Bugs: ·
The watermark is not positioned correctly ·
Coversheet is not output when Solution Details or Project Details are selected |
||||||||||
|
8.1.61 |
Fixed Bugs: ·
The watermark is rendered on the top of
text rather than other way round ·
Environment variables specified in the
coversheet as %variablename% are not expanded ·
Page number are not output unless Print
Table of Contents option is selected Enhancements: ·
A new macro has been provided to output
Project and ProjectItem’s last modified date & time on the page
header/footer. Modified on {ProjectItem Last Modified} The easiest way to achieve this is as follows: 1. Select
Options from the VSNETcodePrint menu 2. Select
Header Footer from
the options node 3. Select
Header or Footer node as appropriate 4. Select
{ProjectItem Last Modified} from
the macro dropdown list 5. Modify
the selected value {ProjectItem Last
Modified} to Modified
On {ProjectItem Last Modified}. Remember that Modified On is only a suggestion. You can
enter any text that you wish appropriate. |
||||||||||
|
8.1.60 |
Fixed Bugs: ·
Sometimes the Addin throws an unhandled
exception when the Table of Contents (TOC) option is selected ·
The Right Hand Side page header/footer text
does not align correctly ·
Remove traces ·
Sometimes only 3 pages are printed of TOC
is selected |
||||||||||
|
|
|
||||||||||
|
8.1.59 |
Fixed Bugs: ·
Print Page Header Footer with the specified
fonts ·
If a source code line is longer than the page
width/column then the wrapped source code is not aligned correctly ·
Sometimes the Addin throws an unhandled
exception when the Table of Contents (TOC) option is selected ·
If a project contains a lot of files that
are excluded from processing using by setting the ‘Exclude Files and Folders’
option then the Addin appears to be looping while these files are skipped ·
The entries in the TOC are not sorted ·
If you cancel the preview then the page
numbers in the page header/footer are not shown ·
Make sure all pages are printed |
||||||||||
|
8.1.57 |
Fixed Bugs: ·
Page numbers are not printed when Print
menu is selected to print source code ·
A number of page are not printed when Print
menu option is selected ·
Connecting lines are not drawn correctly
for a property that is declared with Private qualifier as shown below: Public Property x1() As Long Get Return 1 End Get Private Set(ByVal value As Long) End Set End Property |
||||||||||
|
8.1.56 |
Fixed Bugs: ·
By default all nodes are
expanded in the custom selection treeview window which is not desirable for
solutions and projects with large number of items ·
Page numbers in the
header/footer are not output if PrintTOC option is not selected ·
The pages of table of contents
(TOC) are now numbered as n
of m and pages numbers are output in roman numerals ·
All pages apart from the pages
for table of contents (TOC) are now numbered as n of m ·
The following error occurs when
.aspx file is previewed, printed or exported: ·
The following error occurs when
‘Custom Selection’ is selected for some projects |
||||||||||
|
8.1.55 |
Fixed Bugs: ·
Some registration codes are not
accepted ·
Exclude folder and files no
longer works |
||||||||||
|
8.1.54 |
Fixed Bugs: ·
Icons displayed for CSharp and
JSharp projects and project items are incorrect in the custom selection
solution browser ·
The page numbers in the TOC are
incorrect for some items |
||||||||||
|
8.1.53 |
Fixed Bugs: ·
The page number if assigned to
the right hand side in the page header/footer is not output in the correct
position ·
The page number for the first
line of TOC is incorrect |
||||||||||
|
8.1.52 |
Fixed Bugs: ·
Clicking the Print button on
the Preview window of an ASP.NET project only prints 2 pages. ·
A number of exception errors
have been fixed ·
Correct icons are used for C#
and J# classes, modules in the custom selection solution explorer ·
Radio buttons in the Advanced
tab of Options overlap ·
Use XML Doc Comments font setting when rendering XML Enhancements: ·
Page
Numbering The Addin collects the information for the Table of
Contents (TOC) as the source code is formatted and output. Once all the
selected source code is output, the TOC is generated and moved to the front
of the generated output. This means that the page numbers in the TOC do not
match the actual page numbers in the generated output. The Addin has been enhanced so that the page
numbers in the TOC match the real page numbers in the generated output. Also
the page numbers in the page header/footer match the page numbers in the TOC.
·
Configuring
Fonts There has been a bit of confusion in the use of Use IDE Editor Font Settings checkbox on the Fonts tab of options. An attempt has been made to
remove this confusion. VS.NETcodePrint 2005 is released default settings
for Fonts to be used for generating the output. You can customize the font
attributes for each item (Comment, Identifier, Text etc). The changes that
you make to font attributes will be remembered by the addin and used for all
future printouts. If you prefer the addin to use the font attributes
that you have set in the Visual Studio’s Options (Environment -> Fonts and
colors) then you can do the following: ·
Select the check box Use IDE Editor Font Settings. This will cause the addin to use the font attributes that you have set
in the Visual Studio. You can deselect check box Use IDE Editor Font Settings to revert back to the settings stored in the addin’s options. ·
Click on Copy IDE Editor Font settings button to overwrite the Addin’s current font settings with the font
settings that you have set in the Visual Studio Editor. The addin will use these font settings for
all future printouts until you change them again. |
||||||||||
|
8.1.51 |
Fixed Bugs: ·
An attempt to preview a
Miscellaneous file results in error message “The path is not of legal form” ·
Connecting lines are not drawn
correctly for a property that is declared with Private qualifier as
shown below: Public Property x1() As Long Get Return 1 End Get Private Set(ByVal value As Long) End Set End Property ·
Connecting lines are not drawn
correctly if a parameter name of a procedure ends with: Sub, Function, Namespace, Class, Module, Enum, Property,
Structure or Interface Friend Sub OutputSystemFunction(ByVal
oFunction
As UDF) End Sub ·
An attempt to preview a
Miscellaneous file ( a file that is opened in the IDE by opening it from the
Windows Explorer) results in error message below: Message: Object reference not set to an
instance of an object. ·
The following error is reported
when printing, previewing or exporting code: ·
Sometimes an error message Option for Key ‘Options/Indenting/HTML’ is not found is displayed. ·
Sometimes an error message Option for Key ‘Options/Indenting/XML’ is not found is displayed ·
Printer name is not remembered
between IDE reloads The following error is reported when printing,
previewing or exporting a class diagram file: |
||||||||||
|
8.1.50 |
Fixed Bugs: ·
The following error is reported
when printing, previewing or exporting code: ·
Sometimes an error message Option for Key ‘Options/Indenting/HTML’ is not found is displayed. ·
Sometimes an error message Option for Key ‘Options/Indenting/XML’ is not found is displayed ·
Printer name is not remembered
between IDE reloads ·
The following error is reported
when printing, previewing or exporting a class diagram file: |
||||||||||
|
8.1.48 |
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 ·
‘Format Source Code’ option is
not remembered between VS.NET IDE reloads |
||||||||||
|
|
|
||||||||||
|
8.1.47 |
Fixed Bugs: ·
When the ‘Show Toolbar’ menu item
is selected then the bitmap on the menu item is not shown correctly. ·
Sometimes the following error
is reported when previewing a C# project item: Message: Item has already been
added. Key in dictionary: '82' Stage: at
VSNETcodePrint2005.clsCodeProcessor.getOutlines(Document doc) |
||||||||||
|
8.1.46 |
Fixed Bugs: ·
Sometimes printing, previewing
or exporting a ProjectItem does not generate any output. The preview windows
flicker. ·
Sometimes the following error
is reported when previewing a C# project item: Message: Item has already been
added. Key in dictionary: '82' Stage: at
VSNETcodePrint2005.clsCodeProcessor.getOutlines(Document doc) |
||||||||||
|
8.1.45 |
Fixed Bugs: ·
Export only exports 3 pages ·
Event declarations are not
included in the TOC ·
The Addin results in an error
if an attempt is made to print, preview or export Project Item declarations ·
The Visual Basic icons are
displayed for CSharp project items in the custom selection treeview |
||||||||||
|
8.1.44 |
Fixed Bugs: ·
Export only exports 3 pages |
||||||||||
|
8.1.43 |
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 |
||||||||||
|
8.1.41 |
Fixed Bugs: ·
The Addin gives error
“Attempted to read or write protected memory…” |
||||||||||
|
8.1.40 |
Fixed Bugs: ·
Installing an upgrade the Addin
overwrites the user specified options ·
Some upgrade codes are not
accepted |
||||||||||
|
8.1.36 |
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 Customize 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 ·
If code element (a class, module,
procedure, property) has attributes associated with it and they split over
multiple lines then the divider lines is drawn before the procedure
declaration instead of before the comments associated with the code element |
||||||||||
|
8.1.34 |
Fixed Bugs: ·
The Print menu of Addin behaves the same
as Preview |
||||||||||
|
8.1.33 |
Fixed Bugs: ·
The buttons on the Fonts panel
that allows the font attributes to be changed from the Options configuration
are missing |
||||||||||
|
8.1.32 |
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 ·
Some
upgrade registration codes are not accepted |
||||||||||
|
8.1.31 |
Fixed Bugs: ·
Class, Namespace and Procedure
divider lines are drawn at the wrong line in the generated output ·
Connecting lines are not drawn
when connections flow from one page to the next |
||||||||||
|
8.1.30 |
Fixed Bugs: Items in a ‘Solution Folder’ under a Project are not processed or shown
in the custom selection tree. An attempt to preview a solution with sub
projects fails with error “The path is not of a legal form” |
||||||||||
|
8.1.29 |
Fixed Bugs: The VSNETcodePrint menu is not always created |
||||||||||
|
8.1.28 |
Fixed Bugs: ·
Indenting options for the Text
Editor’s Language in the IDE are not amendable from the VSNETcodePrint’s
Formatting/Indenting options tab ·
The source code is formatted
more frequently than necessary ·
If an option is selected not to
output the source code in closed Outlines then this functionality does not
work when a Namespace, Class or Module is selected for processing ·
The VSNETcodePrint does not
install if ‘My Document’ is not on C: drive |
||||||||||
|
8.1.27 |
·
Clear the bug that caused some upgrade
registration code to be rejected. This version requires Visual Studio - Release Candidate. |
||||||||||
|
8.1.26 |
·
Rebuilt the VSNETcodePrint with
the release Visual
Studio - Release Candidate. |
||||||||||
|
8.1.24 |
Fixed Bugs: ·
Connecting lines are drawn
correctly if the ‘If statement does not end with ‘End If’ and contains
<> in the comparison as shown below: If keyword <> ”End” Then Keyword=”Begin” ·
Restriction has been lifted to
show Outlined source code. |
||||||||||
|
8.1.23 |
Enhancement: An option has been implemented to specify patterns to exclude files and
folders to be excluded when a project is printed, previewed or exported. Each
pattern must appear on a separate line. The syntax for the pattern is the
same as the pattern for the .NET LIKE verb (i.e. filename LIKE pattern). The
source code files and folders that match any of the patterns will be excluded
for processing when a project is printed, previewed or exported. Characters
in pattern Matches in string
A group of one or more characters (charlist)
enclosed in brackets ([ ]) can be used to match any single character in
string and can include almost any character code, including digits. Please note that pattern lines that start with ' or // are treated
as comments. Example 1: // Excludes all files in folders Properties & My Project
*\My Project\*.* Example 2: // Patterns excludes: // All files in folder Properties // All files that has .resx
extension // All
designer files *\Properties\*.* *.resx *.designer.* To excluded a set of files and folders from previewing, printing or
exporting, follow the following steps: |
||||||||||
|
8.1.22 |
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 ·
Keyword ‘Partial’ not output in
Keyword color ·
Connecting lines for class that
starts with Partial keyword is not drawn correctly ·
Forms designer code in files
*.Designer.* is output even if option ‘Output Windows generated code’ is
unchecked. ·
Custom selection window does
not show folders ·
Forms designer code in files
*.Designer.* is shown in the custom selection window even if option ‘Output
Windows generated code’ is unchecked |
||||||||||
|
8.1.21 |
Integrated to work with Visual Studio 2005 Beta2 |
||||||||||
|
8.1.20 |
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
Get
End Get End Property |
||||||||||
Known Issues:
1.
If you select Options.Format and Indenting from VSNetcodePrint menu and then
check Format source code checkbox
then a bug in the Visual Studio 2005’s IDE, sometimes, does not provide the
correct information about the Outlines in the formatted source code. This will
cause the printed source code to show Outlines on the wrong lines.
Workaround:
Select Options -> Format and Indenting and then uncheck
Format source code checkbox
OR
Format the
source code manually, using the Edit.Format
Document command from the menu, before printing it.