VS Law .NET 1.0 Release Notes

This page documents the service patches, bug fixes and enhancements made to the VS Law .NET 1.0 products. (Note: Service patch updates can only be applied to an existing full installation of a VS Law .NET product. Only the latest service patch need be applied.)

VS Law Workstation

VS Law Workstation 1.0

VS Law Workstation Service Patch 1.0.61130.0 (951K) Build 1.0.61130.0 posted 02-Dec-2006 Fixed: When modifying 'Group By' settings in Violations View the checked status of menu items was not always updated correctly. Fixed: When selecting a rulebase file on the review options dialog prior to performing a review, the browse button did not work when the target rulebase was already in the drop-down list. The chosen file was ignored and the selected rulebase in the drop-down list was not changed. Fixed: The VS Law 'Standards Document' menu option was never enabled. Fixed: Parser error when parsing a 'Delegate' statement which was not defined within a type declaration.

Build 1.0.60506.0 posted 19-May-2006 Fixed: VB.NET 2003 Parser failed on 'For Each' statements which declared an array loop variable. Enhanced: Changed default work bench view to violations view for initial installation. This is slightly more helpful for new users. Enhanced: Added registry switch to allow 'Case' statements to be optionally excluded from cyclomatic complexity totals. To enable this feature edit your registry to add a new string value item named "ExcludeCaseFromCyclomatic" with a value of "1" under HKEY_LOCAL_MACHINE\Software\Visible Progress\VS Law\1.0

Build 1.0.60127.0 posted 30-Jan-2006 Fixed: Improved robustness of review process including handling of missing and unresolved assemblies. Fixed: Error System.NullReferenceException: 'Object reference not set to an instance of an object.' in function 'LogMessage' occasionally when cancelling a review. Fixed: VB projects that had all upper-case filenames were not being recognised as supported projects. Enhanced: Rebuilt for changes made to core components for VS Law Batch Processor.

Build 1.0.51120.0 posted 20-Nov-2005 Fixed: Naming conventions with suffix rules were not executed correctly. Fixed: Naming convention rules attached to the CurrentType parser object were not always executed. Fixed: Parser now correctly handles nested classes marked 'NotInheritable'. Fixed: Parse errors occasionally caused by incorrect handling of escaped keywords. Enhanced: Parser error handling and logging improved.

Build 1.0.51005.0 posted 07-Oct-2005 Fixed: Naming conventions now correctly treat digits in names as word separators. Fixed: Parser now correctly handles multiple Inherits statements within an Interface type. Fixed: Parser now handles array variables correctly when the array modifier is placed on the type specifier including group variable declarations (e.g. "Dim a, b, c As Integer()"). Fixed: Parser now correctly handles procedure declarations with missing parentheses.

Build 1.0.50828.0 posted 01-Sep-2005 Fixed: System.NullReferenceException that could occur when attempting to test whether projects have unsaved changes prior to a review. Fixed: System.NotImplementedException that could occur when attempting to test whether projects have unsaved changes prior to a review. Fixed: System.ComponentModel.Win32Exception that could occasionally occur when starting a review. Fixed: System.ArgumentException that could occur when parsing certain source code. Fixed: 'Unexpected language token' errors that could occur when parsing certain source code. Enhanced: Added 9 rules to the standards rulebase to check for appropriate XML comments. N.B. the new rules are not included in this patch file, so please download the new rulebase containing them from the downloads page.

Build 1.0.50728.0 posted 03-Aug-2005 Fixed: Violations logged against the project file were not being taken into consideration when determining whether the project passed or failed tolerances. Fixed: The project file statistics were not appearing in the statistics view. Fixed: Dead code rules have been modified to perform case insensitive rather than case sensitive comparisons. Fixed: InvalidOperationException which occurred when selecting Go To Source for a violation on a class declaration line if there was a class attribute on the previous line. Fixed: NullReferenceException in ProcessInitializeComponentMethod. Enhanced: Robustness of form layout parsing.

Build 1.0.50706.1 posted 06-Jul-2005 Fixed: VisibleProgress.VSLaw.NonUniqueKeyException in function State_FileImplementation - occurred where a code entity had the same attribute defined multiple times. Fixed: System.IO.IOException in function LoadProjectFile - occurred where source files had non-ASCII characters in the name. Fixed: System.Data.OleDb.OleDbException in function Status_EndCodeReviewFile - occurred in non-English locales where a comma is used as the decimal separator. Fixed: System.ArgumentException in function IDE_SolutionOpened - occurred when an IDE project object did not have a FullName property. Fixed: System.NullReferenceException in function IDE_SolutionOpened - occurred where the IDE solution object or the projects collection on the solution object was null.

Build 1.0.50628.5 posted 28-Jun-2005 Enhanced: Removed the requirement for setting the always on top property on the review options and review progress dialogs during a review.

Build 1.0.50621.2 posted 21-Jun-2005 VS Law Workstation 1.0 release.

Known Issues / Limitations

1. Go To Source for Assembly attribute rules should go to the AssemblyInfo.vb file rather than the project properties dialog.
2. If a Windows Form has properties that are stored in a resource file rather than directly in source code, then VS Law does not read them.
3. VS Law does not parse source code according to conditional compilation directives i.e. all code is parsed regardless of conditional compilation constant values and compiler directives.
4. Arrow keys sometimes do not work in the workbench violations or statistics grid. You may use the Return key as an alternative. This is an issue with the grid control when hosted within the Visual Studio IDE and we are currently seeking a solution.

VS Law Batch Processor

VS Law Batch Processor 1.0

VS Law Batch Processor Service Patch 1.0.61130.0 (685K) Build 1.0.61130.0 posted 02-Dec-2006 Fixed: When modifying 'Group By' settings in Violations View the checked status of menu items was not always updated correctly. Fixed: When selecting a rulebase file on the review options dialog prior to performing a review, the browse button did not work when the target rulebase was already in the drop-down list. The chosen file was ignored and the selected rulebase in the drop-down list was not changed. Fixed: Parser error when parsing a 'Delegate' statement which was not defined within a type declaration.

Build 1.0.60309.0 posted 19-May-2006 Fixed: VB.NET 2003 Parser failed on 'For Each' statements which declared an array loop variable. Enhanced: Changed default work bench view to violations view for initial installation. This is slightly more helpful for new users. Enhanced: Added registry switch to allow 'Case' statements to be optionally excluded from cyclomatic complexity totals. To enable this feature edit your registry to add a new string value item named "ExcludeCaseFromCyclomatic" with a value of "1" under HKEY_LOCAL_MACHINE\Software\Visible Progress\VS Law\1.0

Build 1.0.60127.0 posted 30-Jan-2006 VS Law Batch Processor 1.0 release.

Known Issues / Limitations

1. Drag and drop of project files onto the batch project list sometimes fails after repeated drag and drop operations from Windows Explorer search results.

VS Law Administrator

VS Law Administrator 1.0

VS Law Administrator Service Patch 1.0.61130.0 (773K) Build 1.0.61130.0 posted 02-Dec-2006 Fixed: Changing only the case of text within a rule condition did not save the updated rule condition.

Build 1.0.60309.0 posted 19-May-2006 Enhanced: Rebuilt for changes made to core components for VS Law Workstation and Batch Processor.

Build 1.0.60127.0 posted 30-Jan-2006 Enhanced: Rebuilt for changes made to core components for VS Law Batch Processor.

Build 1.0.51120.0 posted 20-Nov-2005 Enhanced: Added IsDisposable() and BaseIsDisposable() methods to CurrentType parser object.

Build 1.0.51005.0 posted 07-Oct-2005 Enhanced: Added DelegateName property to the Naming Conventions property list. Enhanced: Rebuilt for changes made to core components.

Build 1.0.50828.0 posted 01-Sep-2005 Fixed: Reset cursor to default after generating rulebase documentation. Fixed: System.NullReferenceException when showing/hiding the toolbars. Enhanced: Added new property XmlCommentBlock to the Source parser object to get the XML comment block from a type or member as a string that can be loaded into an XmlDocument. Enhanced: Added import for System.Xml to the condition editor.

Build 1.0.50728.0 posted 03-Aug-2005 Enhanced: Rebuilt for changes made to core components.

Build 1.0.50706.1 posted 06-Jul-2005 Fixed: Rule list context menu always correctly enables/disables options according to whether rules are selected or not. Fixed: Confirmation now required before rules can be deleted with the delete key.

Build 1.0.50628.5 posted 28-Jun-2005 Enhanced: Rebuilt for changes made to core components in support of the removal of the always on top requirement for the review options and review progress dialogs in VS Law Workstation.

Build 1.0.50621.2 posted 21-Jun-2005 VS Law Administrator 1.0 release.

Known Issues / Limitations

1. Reserved words in the condition editor are sometimes incorrectly syntax coloured when they are used within the parser object property references e.g. 'Parser.Objects.Property.Name' will highlight 'Property' as a keyword. This happens when an existing condition is edited rather than when newly created.