Visual UML version 4.3 Update Release Notes

 

Version 4.33 Release (Build #566 – July 17th, 2006)

 

1.       Fixed a problem reverse-engineering VB6 classes that contained a Property Procedure declaration that was completely defined on a single-line, using colons to separate the Property Procedure declaration, the Property Procedure body code and the End Property statement, like in the following example:
Public Property Get Items() As clsAnotherClass: Set Items = oItems: End Property
(Also fixed in version 5.01)

2.       Fixed a problem that could result in an Overflow Error #6 and program termination when trying to Print or Print Preview Sequence diagrams. (Also fixed in version 5.01)

 

3.       The active diagram window is now properly updated after using the Printing Options dialog box via the Printing Options command in the main File menu. (Also fixed in version 5.01)

 

4.       Fixed a problem that could result in a runtime error when generating XSD code for a Class with Stereotype = “XSDsimpleType” if that Class was connected to another Class by an Association with no End Role name. (Also fixed in version 5.01)

 

5.       Fixed a problem that could result in a runtime error when generating XSD code for Classes located in the Root of the Model rather than in a Package. (Also fixed in version 5.01)

 

Version 4.32 Release (Build #565 – May 30th, 2006)

 

1.       Fixed some problems that would result in errors (# 457) when reverse-engineering code (C#, VB.NET, Java) into Packages that included a period (“.”) in their names when classes being reverse-engineered referenced other classes via inheritance, realization (interface implementation) or association and the options to derive generalizations or associations was set to on.

 

2.       Improved determination of appropriate referenced classes in packages (including .NET Framework) during reverse-engineering of C#, VB.NET and Java code. No longer confined to classes in packages in or below the Package that the code is being reverse-engineered into. For example, if you have the .NET Framework in the root model package and are reverse-engineering into a lower-level Package, references to .NET Framework classes will be resolved to the existing .NET Framework classes rather than creating new ones in the Package being reverse-engineered into.

 

3.       Fixed a problem reverse-engineering VB6 classes that contained a Property Procedure declaration that was completely defined on a single-line, using colons to separate the Property Procedure declaration, the Property Procedure body code and the End Property statement, like in the following example:
Public Property Get Items() As clsAnotherClass: Set Items = oItems: End Property

4.       Fixed a buffer overflow problem in the file selection dialog box when selecting a large number of VB6 code files to reverse-engineer.

 

5.       Fixed some problems selecting (using the marquee selection method) single Activations on Lifelines of Objects on Sequence diagrams. Plus, subsequently deleting them.

 

6.       Fixed some problems selecting (using the marquee selection method) single State Invariants on Lifelines of Objects on Sequence diagrams. Plus, subsequently deleting them.

 

7.       Fixed problem with ‘Append Comments To Member Definitions’ option in Code Generation Options dialog box not being set correctly upon re-entry.

 

8.       Fixed error # 438 problem that would occur when trying to access Requirements or Test Cases for Attributes or Operations in Classes.

 

9.       Implemented a workaround for a bug in the MySQL ODBC Driver v3.51 that could result in errors when reverse-engineering Foreign Key (FK) Relationships between Tables and in the resulting Classes and Class diagram.

 

10.   Fixed a problem that would result in an error # 91 when trying to import a project from Case Complete that did not have a Package in the root of the project.

 

11.   When importing a project from Case Complete 2.5 that has Actors, Use Cases, etc. with Links to files or URLs, those Links become Links attached to the corresponding Visual UML model objects.

 

12.   No longer get a message box stating that no code files could be found when using a C# project file (.csproj) or a VB.NET project file (.vbproj) for Visual Studio 2005 when using Visual UML is stand-alone mode (as opposed to an add-in to Visual Studio 2005).

 

 

13.   Added SByte, UInteger, ULong and UShort to the list of available supported data types for VB.NET in support of Visual Studio 2005.

 

14.   Added a Testing Profile. To load it, choose Profiles à Open and choose the ‘Testing Profile.Xml’ file from the Profiles subdirectory.

 

Version 4.31 Release (Build #564 – October 25th, 2005)

 

1.       Fixed some problems running Visual UML as an add-in to Visual Studio 2005.

 

2.       Fixed a problem that would result in Visual UML continuing to run after closing after an already running instance of itself was “probed” for (to determine if running or not) by an external application using GetObject. This in turn would result in a “Visual UML is already running!” message when attempting to restart Visual UML after closure, even though the Visual UML user interface was not visible.

 

3.       Updated sample VB6 projects showing how to determine if Visual UML is running, get a currently instance of Visual UML (using GetObject) or start a new instance of Visual UML (using CreateObject).

 

4.       Updated UI control fixes some minor UI problems, including a problem that would cause the main menus not to drop-down if clicked on using a mouse configured for left-handed use.

 

5.       Fixed some problems parsing Java code files.

 

6.       Assorted bug fixes.

 

Version 4.3 Release (Build #563 – August 11th, 2005)

 

1.       Fixed some problems parsing Java and VB.NET code files.

 

2.       Renamed the “Reverse-Engineer Code” sub-menu in the main Tools menu to “Reverse-Engineer”.

 

3.       Fixed some problems with loss of descriptions and tagged values when importing XMI files that were exported by certain other products (such as Case Complete) using the UML 1.4 format.

 

4.       Much better and higher level of integration between Case Complete (2.0) and Visual UML, especially via the XMI interface which is now a lot more viable for migrating use case models from Case Complete (version 2.0) to Visual UML. Note: The following enhancements to the Case Complete, in particular those achieved by using XMI, are dependent on using version 2.0 of Case Complete.