Writing Add-Ins for Visual Studio .NET

Chapter 2: Getting Started with the Add-in Wizard

Figure 2-1: Selecting the project

Figure 2-2: The Add-in Wizard's welcome window

Figure 2-3: Selecting the base language

Figure 2-4: Selecting a host application

Figure 2-5: The Enter a Name and Description dialog box

Figure 2-6: Customizing the add-in

Figure 2-7: Creating an About box

Figure 2-8: Summary of selected options

Figure 2-9: Registry entry for your add-in

Figure 2-10: Directory hierarchy

Figure 2-11: Add-in Manager dialog box

Figure 2-12: Add-in menu item

Figure 2-13: Setup Wizard welcome window

Figure 2-14: Selecting the setup directory

Figure 2-15: Confirming the installation path

Figure 2-16: The setup is complete.

Chapter 3: The Smart Desktop Add-in

Figure 3-1: Adding a Windows Form

Figure 3-2: Configuring the Windows Form

Figure 3-3: Form property page

Figure 3-4: Placing a TreeView control

Figure 3-5: The resized TreeView control

Figure 3-6: Configuring the TreeView

Figure 3-7: The completed TreeView

Figure 3-8: Select the code for commenting.

Figure 3-9: The commented code

Figure 3-10: Code block marked as changed

Figure 3-11: Code block marked by Block Delete

Chapter 4: Debugging an Add-in

Figure 4-1: The Debugging General Options dialog box

Figure 4-2: The Edit and Continue Options dialog box

Figure 4-3: IDE error notification

Figure 4-4: Compiler-detected error

Figure 4-5: Errors in the Output window

Figure 4-6: Error automatically highlighted in the code window

Figure 4-7: Breakpoints beyond an error line

Figure 4-8: Breakpoints ignored in bad code

Figure 4-9: Just before pasting the deleted block

Figure 4-10: Deleted block pasted back to the code window

Figure 4-11: Adding the Proc Error Handler node to the TreeView

Figure 4-12: Select the procedure to receive an error handler.

Figure 4-13: Error handler placed in Sub Test()

Chapter 5: Manipulating Code in Windows

Figure 5-1: Code sample to use the VirtualPoint example

Figure 5-2: VirtualPoint code example message

Figure 5-3: Module before the insertion of a module-level variable

Figure 5-4: Module after the variable is inserted

Figure 5-5: New method added to the end of a module

Figure 5-6: Selecting the procedure to be cloned

Figure 5-7: CloneProc form

Figure 5-8: Cloned procedure

Chapter 6: Manipulating Controls on Forms

Figure 6-1: Registry pointer to project templates

Figure 6-2: Newly created project

Figure 6-3: Buttons placed on the form

Figure 6-4: Default size of btn1

Figure 6-5: Button resized and repositioned

Figure 6-6: Showing the button's new text and name

Figure 6-7: Btn2 removed

Figure 6-8: Selected component and the count of selected components

Figure 6-9: Displaying properties of selected component

Figure 6-10: Accessing Designer properties in the Options dialog box

Figure 6-11: Completed form

Chapter 7: The User Interface

Figure 7-1: UIMenus add-in menu items

Figure 7-2: Add-in toolbar

Figure 7-3: Picture container form

Figure 7-4: Office CommandBar

Figure 7-5: Office menu

Figure 7-6: Form with a NotifyIcon and a ContextMenu

Chapter 8: The Macro Explorer and the Macros IDE

Figure 8-1: Macros menu

Figure 8-2: Form1 and controls

Figure 8-3: Macro Explorer pop-up menu

Figure 8-4: Windows closed by macro

Figure 8-5: Form1 with buttons randomly placed

Figure 8-6: Form1 with buttons realigned

Figure 8-7: Code block before commenting

Figure 8-8: Code block commented by the macro command

Figure 8-9: The Macros IDE

Figure 8-10: Automatic selection of a whole procedure by a macro

Figure 8-11: Clone procedure display form

Figure 8-12: New cloned procedure

Figure 8-13: Documented code

Chapter 9: Manipulating Projects

Figure 9-1: Running the CreateSolution1 macro

Figure 9-2: New Windows application project

Figure 9-3: ProjectItem for Form1.vb

Figure 9-4: ProjectItem for Form1.resx

Figure 9-5: Module1 added to the project

Figure 9-6: Form2 added to the project

Figure 9-7: Class1 added to the project

Figure 9-8: Adding a postbuild rule

Figure 9-9: Notepad loaded as pre- and postbuild processes

Figure 9-10: Adding items to the Task List programatically

Figure 9-11: Copying a code snippet

Figure 9-12: Pasting the code snippet

Figure 9-13: New pane in the Output window

Figure 9-14: ForceItemsToTaskList example

Chapter 10: Multiple Languages in Add-ins

Figure 10-1: External Tools dialog box

Figure 10-2: Launching an external tool

Figure 10-3: C# Form1

Figure 10-4: Running the C# digital clock

Figure 10-5: DLL project added to the add-in solution

Figure 10-6: Adding a reference to the DLL project

Figure 10-7: Message displayed from the Visual Basic DLL

Figure 10-8: C# block commented code

Figure 10-9: CloneProc form with the C# procedure being cloned

Figure 10-10: Cloned C# procedure inserted in the class

Chapter 11: Handling Automation Events

Figure 11-1: Reminding the user to change the name of Form1

Figure 11-2: Task List activated by code with errors

Chapter 12: Putting It Together—Let's Build a Real Add-in

Figure 12-1: Comment menu form

Figure 12-2: Displaying the Comment menu form

Figure 12-3: The selected block has been commented.

Figure 12-4: Entering context comments

Figure 12-5: Inserted context comments

Figure 12-6: The frmWindowsMenu form

Figure 12-7: MessageBox Designer form

Figure 12-8: The MessageBox Designer in action

Figure 12-9: MessageBox Designer–generated Visual Basic code

Figure 12-10: Testing the MessageBox Designer

Figure 12-11: MessageBox Designer–generated C# code

Figure 12-12: The About NET Desktop box

Figure 12-13: The UserControl's designer

Figure 12-14: Default form name detected

Chapter 13: Migrating VB 6.0 Add-ins to .NET

Figure 13-1: Error message encountered when trying to load a VB 6.0 add-in

Figure 13-2: Upgrade errors shown in the Task List

Figure 13-3: The no start-up project error message

Figure 13-4: Setting a start-up project in the Project Properties dialog box

Figure 13-5: Using Regasm.exe to register an add-in

Figure 13-6: B 6.0 form upgraded to a .NET form