MZ-Tools provides many benefits to developers (individual or inside a team) and team leads:

Code faster: with customizable code templates, headers, exception/error handlers, etc.
Design faster: with designers to set quickly the name, caption, tabindex and other default properties.
Find code faster: with unlimited output windows with trees of results, either to search code, method callers, etc.
Generate documentation: in either XML or customizable HTML output formats.
Ensure quality and standards: define standards through flexible rules and ensure that the team follows them.

Thousands of satisfied developers worldwide have found MZ-Tools to be invaluable. It is used by developers inside of companies such as:

Intel
UPS
Nielsen
HP
US Air Force
Sprint
Cisco
Bridgestone
Capital One
Bayer
Ricoh
ExxonMobil
Fedex
Roche
Pfizer
FAA
Alstom
ABB

MZ-Tools can find strings in a method, file, project, solution or project group, selected text, group of files or group of projects. The results are shown in the following results window, much more convenient than the one provided by the Microsoft IDEs.

The results window provides multiple tabs to store all your previous searches (which you can remove too), instead of just two output panes. You can refresh the results at any time, copy them to the clipboard (to paste them in Microsoft Excel, for example), or export them to a file. You can also remove results from the list if they are not of interest, in order to see only the ones that you want to examine more carefully. You can also select if you want to see the hierarchy of code elements (class, method, etc.) where an occurrence has been found, or just the file.

From the results window after a search, you can replace the occurrences found with a new string, one by one or all at the same time. With this two-step approach, you can exclude occurrences from the list (by simply deleting them) before the replacement operation.

MZ-Tools can find all locations in your source code where a method is called. The results are shown in the following results window, much more convenient than the one provided by the Microsoft IDEs.

You can create code templates for code snippets that you use frequently, both in a Personal code library or in a Team code library shared by all team members. To insert a code template in your source code, you can select it from a treeview with all code templates, or for greater productivity you can either use an expansion keyword or a keyboard shortcut.

Code templates can include predefined variables (such as author, current date, method name, cursor position after insertion, etc.) but can include also user-defined variables, that is, your own variables. When you insert in the source code a code template with user-defined variables, a dialog asks you the values of those variables.

For VBA, VB6 and VB5, the code indenter can set the correct indentation to each line of a method, file or project. There is even a line intentation review that can pinpoint which lines of code have an incorrect indentation.

With this window, you can choose the values of the enum expression which require a separate "case" statement and you can choose the order of the enum values. If you leave enum values not selected, a default (C#) or Case Else (VB.NET / VB / VBA) statement is added.

You can add or remove line numbers to the source code of a method, class, file, project or solution to use the undocumented Erl function of VB.NET / VB / VBA in your error handlers (using the On Error GoTo statement). This allows you to know the exact line number that caused the error.

Only for V.I.P