I guess that it depends on what you want the buttons for. If you're simply looking to add a couple of buttons to all of the pages of the wizard (e.g. a Help button), you can simply bung it straight onto the class that you derived from WizardSheet.
If you're looking for a couple of buttons that behave like Back and Next, you'll (again) need to bung them on the WizardSheet (or the derived class), and you can add button-specific Enable methods to that class. For example, you might have an EnableHelpButton method.
Alternatively, add some extra bit flags to the enum, and change the implementation of SetWizardButtons. Note that the current implementation is similar to how MFC wizards work, in that you can't have both the Next and Finish buttons visible at the same time.
Whichever option you choose, you'll need to put button controls onto the form. Defining extra bit fields does nothing magic.
Extra Buttons
I guess that it depends on what you want the buttons for. If you're simply looking to add a couple of buttons to all of the pages of the wizard (e.g. a Help button), you can simply bung it straight onto the class that you derived from WizardSheet.
If you're looking for a couple of buttons that behave like Back and Next, you'll (again) need to bung them on the WizardSheet (or the derived class), and you can add button-specific Enable methods to that class. For example, you might have an EnableHelpButton method.
Alternatively, add some extra bit flags to the enum, and change the implementation of SetWizardButtons. Note that the current implementation is similar to how MFC wizards work, in that you can't have both the Next and Finish buttons visible at the same time.
Whichever option you choose, you'll need to put button controls onto the form. Defining extra bit fields does nothing magic.
There's more than you ever wanted to know about bit fields in .NET on this CodeProject page, or there's this or the documentation for the [Flags] attribute.