Need Data But Not Hardware
You will need sample capture data to exercise the plug-in but do not necessarily need DigiView hardware. If you are using one of the example captures, you should unplug your DigiView or select NO if prompted to convert the file to match your hardware. This reduces complications if the DigiView used to capture the data had more channels than your DigiView.
Disable ALL plug-in based signals
When multiple signals use a single plug-in, DigiView loads a single instance of the plug-in into memory. DigiView will not unload the plug-in until ALL signals using it have been deleted or disabled. It can be annoying to have to disable several signals each time you update the plug-in. Also, each signal will attempt to use the plug-in making it difficult to track exactly which configuration is being debugged. For the smoothest, most consistent debug session, it is usually better to have only one signal enabled at a time that uses your plug-in.
When in debugging mode, DigiView will pause before each plug-in is loaded, giving you a chance to attach a debugger to that specific plug-in. Debugging is simpler if there are no signals using plug-ins except the one you are debugging. Delete or disable all plug-in based signals.
If you already have a signal defined that uses your plug-in, disable it for now, even if you intend to use it for debugging.
Change Solution Configurations to Debug in Visual Studio Express
Turn on Expert settings in Visual Studio Express
Select 'Tools->Settings->Expert Settings' to enable additional debugging options
See the next section for work-flow suggestions.