The Express editions of Visual Studio don't support add-ins (they have
no Add-In Manager). Microsoft did not consider them to be used professionally
(they are intended for students, hobbyists, etc.) and removed support for
add-ins.
There are several ways to customize the MZ-Tools toolbar and its buttons:
- You can hide the toolbar by right-clicking on it and deselecting it from
the list of toolbars in the context menu. This state is preserved among
sessions, so you have to do it only once.
- You can remove buttons from the toolbar by clicking the "Personal
Options" button (or "Options" button, depending on the edition) and going to
the "Toolbar buttons" section. Note: if you remove the Options button, you
can still show this window through the main "MZ-Tools" menu which is near
the "Tools" menu of Visual Studio.
- You can create buttons on other toolbar by clicking the "Tools",
"Customize..." menu, "Commands" tab, "AddIns" section, and drag and drop the
desired command over any toolbar. To customize the style of the button (only
image, image with text, etc.) right-click on it and select the desired
style. Note: ensure that you are using only one Visual Studio instance when
doing this and close it to persist the changes.
- You can create a new toolbar by clicking the "Tools", "Customize..."
menu, "Toolbars" tab, "New..." button, give the toolbar a name and drag and
drop commands over it as explained in the previous step.
By default, MZ-Tools tries to be smart and if it detects that the text
under the cursor is selected text or that the text to search is a code element
name (such as a procedure name, class variable, parameter, etc.), it adjusts the
scope (for example, to Procedure for parameters, or to Class for class
variables) and sets the Match Whole Word and Match Case settings to true. Most
of the time this kind of guessing is desirable (contact us if you find
situations where the guessing performed by MZ-Tools is not suitable).
Nonetheless, you can turn off this behavior in the "Options", "Personal Options"
menu, "Find Text" section, "Initialize search options from the editor" checkbox.
When the checkbox is unchecked, MZ-Tools remembers the last settings rather
than guessing.
To detect all dead code would require the implementation of a parser and a compiler,
which is beyond the functionality of MZ-Tools. Instead, this feature works
by checking that a declaration name does not appear again in the source code. This
approach has a couple of limitations:
- Only private declarations are reviewed (as stated in the help file), since
otherwise the performance would be severely affected.
- If you have two declarations in the same file with the same name (such as
an enum and a class variable), none of them will be reported as unused even if
they are in fact unused.
The bottom line is that a missing report of a dead declaration is not
considered a bug. Only reports of declarations as unused code which are really
used are considered bugs.
Any problem not addressed here? Don't hesitate to ask.
|
