WizGen Add-in for Visual Studio 6.0






4.67/5 (6 votes)
Jul 1, 2000

68574

1069
This Add-in is similar to class wizard but can be used for MFC extension libraries
Introduction
This Add-in is similar to ClassWizard but allows only new classes and overriding of virtual functions. It is useful if you use MFC extension libraries, this makes it easy to create a new class from any extension header files that you have. This is the first version so be prepared for problems.
Setup
- Copy WizGen.dll to any place you want. A good place would be to the Microsoft Visual Studio add-in folder at
Common\MSDev98\AddIns
. NOTE: If you build the project, it will copy it to the add-in folder for you. - Open Visual Studio and select:
Tools | Customize...
- Go to the
Add-ins and Macro files
tab and click on the "Browse" button. - Go to the folder to which you copied WizGen.dll and select it. Make sure the
Files of type
listbox is onAdd-ins (.dll)
. - When closing the dialog, a toolbar will appear with the WizGen button. Using the customize dialog you can move this button to any other toolbar (if you want to).
- Pressing the button will open a dialog box in which you can select the text mode you want to use.
Usage
Before you can start using this add-in you need to analyze your extension header files.- Select
New Wizard File
from the drop-down menu. - Enter a name for the extension library (no extension needed).
- Enter an Export Macro name. This is the
#define
that is used to export the classes eg.AFX_EXT_CLASS
or leave it blank if it's not used. - Enter the location of your class library header files.
It will then generate a list of classes that it found.
You are now ready to create new classes or override virtual functions. If you've ever used ClassWizard or the wizard bar everything should be familiar.
Known Problems
It uses MFC. If that's a problem wait until the next version. Hopefully I will try to remove the MFC dependencies.It asks to reload a newly created header file. If anyone can figure it out let me know.
Update
I think this is a version that actually works. (Though I'm sure someone will tell me it doesn't)Thanks goes to Darren Schroeder for helping me find and fix the bugs.
There is now an option to include the base header file. If you analyze the MFC include files (which is recommended), you will then have access to all MFC virtual functions. It now avoids duplicates.
Send your comments, feedback, and suggestions to philip@masmex.com