Today, June 1, MZ-Tools 220.127.116.11 has been released. This build fixes some minor bugs and introduces some important enhancements:
- For VBA/VB6/VB5 and VS 2010, you are no longer forced to install .NET Framework 2.0 on Windows 10 (or Windows 8 / Windows 8.1 if you are still using those versions). The same MZ-Tools 8.0 binaries can now work on the already installed .NET Framework 4.0 of Windows 8.x/10 and on .NET Framework 2.0 of Windows 7.
- All .NET-based add-ins for the VBA editor of Office (or for VB6/VB5) should use a COM Shim (an intermediate native COM Dll that loads an isolated .NET environment) but unfortunately none of them do it at present. All they share the same .NET environment, which causes crashes between them. MZ-Tools 8.0 for VBA/VB6/VB5 uses now a COM Shim, so it is properly isolated from other .NET-based add-ins.
- For VB/VBA, the code editor of templates, headers, error handlers, etc. uses now the look and feel (font, colors) that you may have customized for the VB/VBA editor.
- For VB/VBA, you can now place MZ-Tools buttons on any toolbar (using the context menu of a toolbar and clicking the Customize… menu item) and they will work after a required restart.
The complete changelog is the following:
MZ-Tools 18.104.22.168 released (June 1, 2016)
- Enhanced [Internal] (VB/VBA): MZ-Tools 8.0 for VB/VBA can now work on Windows 8/8.1/10 using .NET Framework 4.0 (already installed) without forcing the installation of .NET Framework 2.0.
- Enhanced [Internal] (VS): MZ-Tools 8.0 for VS 2010 can now work on Windows 8/8.1/10 using .NET Framework 4.0 (already installed) without forcing the installation of .NET Framework 2.0.
- Enhanced [Internal] (All): The code element header editor now adds the final carriage return if missing.
- Enhanced [#11165] (VB/VBA): Buttons placed by hand on other toolbars (using Customize…) now work (requires restart).
- Fixed [Internal] (VB/VBA): A COM Shim is used now for proper isolation, avoiding conflicts with other .NET-based add-ins.
- Fixed [#11134] (All): The code template editor now colorizes the code on paste operations using Control+V or Shift+Insert keys.
- Fixed [#11136] (All): The code template editor now fills the author field automatically.
- Fixed [#11174] (All): Methods using the Declare modifier or the DllImport attribute were considered as valid methods for the scope selector, when they shouldn’t because they don’t have body.
- Fixed [#11124] (VS): The Favorite Solutions feature didn’t recognize Visual Studio 2015 solutions.
- Fixed [#11125] (VB/VBA): The code template editor now uses the font name, font size, backcolor and forecolor of the VB/VBA editor.
- Fixed [#11007] (VB/VBA): The line indenter didn’t parse correctly methods with the Static modifier.
- Fixed [#11101] (VB/VBA): The line indenter didn’t parse correctly Case Else statements ending with the statement separator “:”.
- Fixed [#11159] (VB/VBA): Error “Failed to get command bar name: CommandBarKinds.EditToolBar” could happen in some cases.
- Fixed [#11187] (VB/VBA): The error handler sample used 3 spaces as indentation (now it uses a tab character).
- Fixed [#11189] (VB/VBA): System.UriFormatException (“Invalid URI: The hostname could not be parsed.”) was not handled friendly by the Task List when using @ssl with a SharePoint site.
- Fixed [#11133] (VBA): The autosave documents feature now sets Application.EnableEvents = false before saving the Excel workbook.