How to: Interpret Visual C++ Wizard Model Examples
Visual Studio add-ins are deprecated in Visual Studio 2013. You should upgrade your add-ins to VSPackage extensions. For more information about upgrading, see FAQ: Converting Add-ins to VSPackage Extensions.
Most examples in the Visual C++ Wizard Model reference topics are excerpts from the wizard HTML files provided in Visual Studio to create Visual C++ projects. Where practical, entire functions are included with the topic to provide a context for the usage. For more information about Visual C++ custom wizards, see Creating a Custom Wizard, Steps to Designing a Wizard, Custom Wizard Samples and Customizing Your Wizard.
To locate other examples of properties and methods in the Visual C++ wizard files, use the Find in Files dialog box.
Note
You can find a folder for each of the Visual C++ wizards in the \Program Files\Microsoft Visual Studio 10.0\VC\VCWizards folder.
The Visual C++ Wizard Model architecture uses script and HTML to implement automation. When you call a method or property from script, you must follow one of the conventions in the following procedures.
Note
The dialog boxes and menu commands you see might differ from those described in Help depending on your active settings or edition. These procedures were developed with the General Development Settings active. To change your settings, choose Import and ExportSettings on the Tools menu. For more information, see Customizing Development Settings in Visual Studio.
To access properties and methods in the Visual C++ Wizard Model from a JScript file
Prepend the model item with "wizard."
For example:
wizard.FindSymbol("PROJECT_PATH");
To access properties and methods in the Visual Studio environment model from a JScript file
Prepend the model item with "dte".
For example:
var Solution = dte.Solution;
To access properties and methods in the Visual C++ Wizard Model or the Visual Studio environment model from an HTML file
Prepend the model item with "window.external."
For example:
window.external.AddSymbol("HEADER_FILE_VALID", true);