|
|
|||
|
||||
|
||||
|
Why doesn't MZ-Tools support the Express editions of Visual Studio? 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. You can review the Visual Studio product line overview. Apparently, the minimal Visual Studio edition that supports add-ins is the Standard Edition ("Extensibility: Consume extensions").
If I install Visual Studio 2008 after having installed MZ-Tools, what must I do to register MZ-Tools for Visual Studio 2008? MZ-Tools targets all Visual Studio versions simultaneously. When you run the setup, it shows a list with checkboxes with the Visual Studio versions it can target, and enables the installed ones. You can then select the ones that you want MZ-Tools to target. If you install a new Visual Studio version (such as Visual Studio 2008) after MZ-Tools was installed, you need to run the setup again to select the new Visual Studio version.
How can I customize the MZ-Tools toolbar and buttons? There are several ways to customize the MZ-Tools toolbar and its buttons:
The Find window does not remember previous settings (Scope, Match Whole Word, Match Case) 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.
The Review Dead Code feature does not detect some dead declarations 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:
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.
Several operations of MZ-Tools seem to hang Visual Studio or cause System.AccessViolationException If you are using the Refactor!, Refactor Pro or CodeRush add-ins from Developer Express, likely their DXCore component is causing this problem, which happens with all add-ins that process files:
COMException can happen sporadically loading or unloading MZ-Tools Typically this problem is not reproducible (otherwise submit a bug to get it fixed) and it happens from time to time when MZ-Tools tries to add or remove its commandbars and buttons during the initialization or shutdown phases. It is caused by internal problems of the Visual Studio commandbars when used from add-ins.
Any problem not addressed here? Don't hesitate to ask. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|
 |
|
