Last May 1 a new monthly build of MZ-Tools, 220.127.116.11, was released. This build continues improving the updating experience initiated some builds ago: first, it provides again a “Download Only” button for those of you who don’t want the new automated update and prefer a manual installation as before. Second, in the automated update, it prevents in many cases the error that happened when some dll was in use, asking you to close the instance of the IDE before updating. And third, it reopens automatically the IDE and the loaded project when the update is finished.
In this build the headers review shows the first line of a header template that causes that the existing header no longer matches that template, which is useful to know why a header review is not passing. It also provides a context menu entry for the Insert Error Handler (VB) or Insert Exception Handler (Visual Studio).
It also introduces a change, in the form of a new requirement: .NET Framework 3.5 (previously only .NET Framework 2.0 was required). But in most cases you won’t need to install it because Windows 7 provides it and on Windows 10 only MZ-Tools 8.0 for Visual Studio 2005 will require it, but not MZ-Tools 8.0 for VBA/VB6/VB5. This new version of the .NET Framework will allow MZ-Tools in the future to use internally better APIs and externally new UI technologies (such as WPF).
Finally, this build fixes quite a few bugs that you have reported during the last month.
The complete changelog is the following:
- Changed (VS 2005): .NET Framework 3.5 is now required if not running on Windows 7.
- Changed (VBA/VB6/VB5): .NET Framework 3.5 is now required if running on Windows XP / Vista.
- Enhanced [#12069] (All): The context menu of the code window now provides the “Insert Exception Handler” / “Insert Error Handler” meny entry.
- Enhanced [#12113] (All): Added new predefined variable Type Tag With Upper Case ($P[TYPE_TAG_WITH_UPPER_CASE]), useful if your constants use upper case and include a type tag.
- Enhanced [#12065, #12070, #12071] (All): The setup now shows a better message to close the IDE that is locking a file when updating.
- Enhanced [#12065, #12070, #12071] (All): The setup now reopens the IDE and project or Office document that was open before closing it for updating.
- Enhanced [Internal] (All): The Headers Review now shows the line of the header template that causes that the reviewed header doesn’t match it.
- Fixed [#12068] (VBA): The Code Explorer didn’t respond to changes in the active file after unlocking a password-protected database. Now clicking the Refresh button starts responding.
- Fixed [#12032] (VBA): In the Control Name Assistant, the Tab key inserted a Tab character in the textbox if a message box was shown (such as invalid name or state loss).
- Fixed [#12081] (All): System.IO.IOException was not handled gracefully when deploying options files to a folder.
- Fixed [#12090] (All): The Browse Folder dialog caused COMException 0x80040111 on Windows 7 if themes were deactivated.
- Fixed [#12096] (VB/VBA): The Headers Review failed in some cases using user-defined variables.
- Fixed [#12106] (All): The Programming Rules Review didn’t locate the exact code when using the “Any of these values” option instead of the “This value” option and didn’t show all violations.
- Fixed [#12103] (VBA): The type tag editor and other features didn’t show 32-bit type libraries when using the 64-bit VBA editor.
- Fixed [#12133] (VS): Shared projects were not supported.
- Fixed [#12123] (VB6/VB5): Several features such as Find Text could crash a project if it contained many forms due to a leak.
- Fixed [Internal] (All): The Headers Review didn’t review if there was more text or lines after the lines of a valid header.
- Fixed [Internal] (VBA): Several features didn’t work correctly with the Page control in some versions of Office.
- Fixed [Internal] (VBA): The Check for Updates feature of the portable edition offered the Install button when it should offer only the Download button.
- Fixed [Internal] (VS): Icon of Keyboard Shortcuts in Options window was not correct when using the dark theme.
- Fixed [Internal] (All): The Programming Rules Review didn’t show a friendly message if some regular expression was not valid.
- Fixed [Internal] (All): The Programming Rules Review didn’t work in some scenarios using the Any Code Element rule kind.