MZ-Tools 3.0 Build 1208 released with bug fixes

Posted on by

MZ-Tools 3.0.0.1208 has just been released with an urgent fix for a bug that was introduced in build 1207. It also fixes a rare bug that could happen on some systems:

  • Fixed: Showing a toolwindow docked caused a System Error &H80004005. This bug was introduced by build 1207.
  • Fixed: The setup caused error 0×5 if MSADDNDR.DLL file was present on the system but was an old version (the setup didn’t replace it with the newest version).

MZ-Tools 7.0 Build 108 released with bug fixes

Posted on by

MZ-Tools 7.0.0.108 has just been released. The list of bug fixes is the following:

  • Fixed: When closing Visual Studio 2010 or higher, a System.InvalidCastException could happen if CodeRush (and maybe other DXCore-based DevExpress products) is also installed.
  • Fixed: The progress bar of results toolwindows appeared below the status bar.
  • Fixed: The status bar of the progress form of some operations was not themed when using the Visual Studio 2012 Dark theme.
  • Fixed: The Find Text dialog didn’t show in the Find combobox the selected text under the cursor if it was a substring of a previously searched string.
  • Fixed: The Sort Code Elements feature didn’t sort correctly assembly attributes (which must be before other code elements).
  • Fixed: The New Method Assistant did not preserve the property style between Visual Studio sessions.
  • Fixed: The Review Code Elements Order feature could cause a NullReferenceException with non-code files.

MZ-Tools 7.0 Build 107 released with bug fixes

Posted on by

MZ-Tools 7.0.0.107 has just been released. The list of bug fixes is the following:

  • Fixed: The Method Callers feature caused “System.ArgumentException: An item with the same key has already been added.” with Web projects.
  • Fixed: The Code Element Headers feature didn’t offer the following predefined variables: “Method Handled Events”, “Method Return Type Name”, “Method Return Type Full Name”, “Method Return Type Aliased Name”, “Method Return Type Prefix”.
  • Fixed: The New Method Assistant didn’t add the fields of new properties in consecutive order.

MZ-Tools 7.0 Build 106 released with bug fixes

Posted on by

MZ-Tools 7.0.0.106 has just been released. The list of bug fixes is the following:

  • Enhanced: The Sort Code Elements feature now preserves existing code regions if you don’t configure it to create regions automatically.
  • Fixed: The Favorite Code Elements toolwindow retained the focus after failing to show a code element that was changed/removed, rather than activating the code window.
  • Fixed: The Sort Code Elements feature caused an exception if a namespace contained duplicated Imports / using statements.
  • Fixed: The Options button on the “Check for updates” error window has been removed since it caused exceptions in Visual Studio 2012.
  • Fixed: The Statistics feature caused an exception when sorting by a column with values with the thousand separator. This bug was introduced in build 7.0.0.103.
  • Fixed: The MessageBox Assistant feature used the inexistent Microsoft.VisualBasic.ControlChars.StringConstants.CrLf constant in multiline texts. This bug was introduced in build 7.0.0.103.

The new “Exclude files generated by Visual Studio” option of MZ-Tools 7 Find dialog

Posted on by

The Find feature of MZ-Tools keeps improving. In the latest build released a new “Exclude files generated by Visual Studio” option has been added:

The Find dialog already offered a “Files matching regular expression (.NET)” scope that was more powerful but the new option is handy if you just want to exclude files that are created by Visual Studio (that is, not really your code).

MZ-Tools 7.0 Build 103 released with bug fixes

Posted on by

MZ-Tools 7.0.0.103 has just been released. The list of bug fixes is the following:

  • Enhanced: The Find feature now has a new setting “Exclude files created by Visual Studio”.
  • Fixed: The Go To Favorite Code Element feature now goes to the original line number even if its text has been changed or deleted.
  • Fixed: Several controls are now flicker-free.
  • Fixed: In the Code Library Options window of Visual Studio 2005, when creating a code template for the JavaScript language a System.ApplicationException exception was thrown.
  • Fixed: In the Code Library Options window of Visual Studio 2005, when creating a code template for the XAML language a System.ApplicationException exception was thrown.
  • Fixed: The button of the color selector control didn’t show the down arrow except in Visual Studio 2012.
  • Fixed: The Find dialog cleared the selected files or projects after a search, so they couln’t be reused in the next search.
  • Fixed: The Find dialog didn’t preselect the whole word under the cursor with some non-English characters.
  • Fixed: The Find feature didn’t work correctly when using the Exclude comments option and the found string was like a comment but inside a literal.
  • Fixed: When you used the Tools, Customize dialog to delete a MZ-Tools toolbar, you got an exception when showing the MZ-Tools, Options dialog, Toolbars and menus section.
  • Fixed: The Sort Code Elements feature didn’t consider VB.NET destructors (Protected Overrides Sub Finalize()).
  • Fixed: On Turkish systems you got “This version of MZ-Tools is not intended for SOFTWARE\MICROSOFT\VISUALSTUDIO\[version]” when loading MZ-Tools.
  • Fixed: The code template editor used “MZTools7.ExceptionHandler” as prefix in the command full name.
  • Fixed: The programming rule editor didn’t allow the .NET Framework 4.5 value for the TargetFramework property of the Project item.

MZ-Tools 3.0.1206 for VBA with bug fix to support Microsoft Office 2013

Posted on by

While the MZ-Tools web site stated some months ago that Microsoft Office 2013 (the Consumer Preview at that time) was supported by MZ-Tools 3.0 for VBA, it has not been until a few days ago that a couple of users reported that the setup caused error “Unable to register DLL/OCX:RegSvr32 failed with exit code 0×5″ on a clean installation.

This problem is caused because Microsoft Office 2013 no longer installs the file MSADDNDR.DLL (in the folder C:\Program Files (x86)\Common Files\designer), which is used by add-ins for the VBA editor. The problem didn’t happen if you had a previous version of Office or Visual Basic 6.0 installed, since both of them installed that file.

The new setup of MZ-Tools 3.0 version 3.0.1206 just released fixes this problem installing that file.

MZ-Tools 7.0 Build 102 released with bug fixes

Posted on by

MZ-Tools 7.0.0.102 has just been released. The list of bug fixes is the following:

  • Fixed: The Insert Code Element header caused NullReferenceException if the cursor was on a using/Imports statement.
  • Fixed: The Options files are now saved in UTF8 encoding rather than in the default (code page) encoding.
  • Fixed: The code editor of code templates didn’t support Unicode characters.
  • Fixed: The Control Explorer didn’t show some icons with the correct color when switching themes in Visual Studio 2012.
  • Fixed: The treeviews and listviews didn’t show the Windows Explorer style.
  • Fixed: The TabPages of TabControls were not themed when using the Visual Studio 2012 Dark theme.
  • Fixed: The headers of ListViews were not themed when using the Visual Studio 2012 Dark theme.
  • Fixed: The ComboBoxes were not themed when using the Visual Studio 2012 Dark theme.
  • Fixed: Web Site projects caused exceptions in the Open Build Output Folder and Dead Code Review features.
  • Fixed: Some features that need to resolve types could cause System.IO.FileNotFoundException.
  • Fixed: You could get System.ArgumentException in the Options window after changing the team options folder in the General section of the Personal Options tab.
  • Fixed: On non-English Visual Studio versions, keyboard bindings of commands that placed buttons on built-in Visual Studio commandbars were lost when MZ-Tools was unloaded.
  • Fixed: The Sort Code Elements feature caused an exception if a file contained duplicated Imports / using statements.
  • Fixed: Usercontrols of the solution could cause “ICollectionItemEditor.InitializeControlValues failed” in the Options window.
  • Fixed: The “Insert >” button of the C# and VB.NET language option pages of the New Method / Property Assistant feature caused the exception “System.ArgumentException: Value does not fall within the expected range” in Visual Studio 2005 and 2008.