Walkthrough: Debugging Custom Windows Forms Controls at Design Time
When you create a custom control, you will often find it necessary to debug its design-time behavior. This is especially true if you are authoring a custom designer for your custom control. For details, see Walkthrough: Creating a Windows Forms Control That Takes Advantage of Visual Studio Design-Time Features.
You can debug your custom controls using Visual Studio, just as you would debug any other .NET Framework classes. The difference is that you will debug a separate instance of Visual Studio that is running your custom control's code
Tasks illustrated in this walkthrough include:
Creating a Windows Forms project to host your custom control
Creating a control library project
Adding a property to your custom control
Adding your custom control to the host form
Setting up the project for design-time debugging
Debugging your custom control at design time
When you are finished, you will have an understanding of the tasks necessary for debugging the design-time behavior of a custom control.
The dialog boxes and menu commands you see might differ from those described in Help depending on your active settings or edition. To change your settings, choose Import and Export Settings on the Tools menu. For more information, see Customizing Development Settings in Visual Studio.
The first step is to create the application project. You will use this project to build the application that hosts the custom control.
To create the project
Create a Windows Application project called "DebuggingExample". For details, see How to: Create a Windows Application Project.
The next step is to create the control library project and set up the custom control.
To create the control library project
Add a Windows Control Library project to the solution.
Add a new UserControl item to the DebugControlLibrary project. For details, see NIB:How to: Add New Project Items. Give the new source file a base name of "DebugControl".
Using the Solution Explorer, delete the project's default control by deleting the code file with a base name of "UserControl1". For details, see NIB:How to: Remove, Delete, and Exclude Items.
Build the solution.
At this point, you will be able to see your custom control in the Toolbox.
To check your progress
Find the new tab called DebugControlLibrary Components and click to select it. When it opens, you will see your control listed as DebugControl with the default icon beside it.
To demonstrate that your custom control's code is running at design-time, you will add a property and set a breakpoint in the code that implements the property.
To add a property to your custom control
Build the solution.
To debug the design-time behavior of your custom control, you will place an instance of the custom control class on a host form.
To add your custom control to the host form
In the "DebuggingExample" project, open Form1 in the Windows Forms Designer.
In the Toolbox, open the DebugControlLibrary Components tab and drag a DebugControl instance onto the form.
Find the DemoString custom property in the Properties window. Note that you can change its value as you would any other property. Also note that when the DemoString property is selected, the property's description string appears at the bottom of the Properties window.
To debug your custom control's design-time behavior, you will debug a separate instance of Visual Studio that is running your custom control's code.
To set up the project for design-time debugging
Right-click on the DebugControlLibrary project in the Solution Explorer and select Properties.
In the DebugControlLibrary property sheet, select the Debug tab.
In the Start Action section, select Start external program. You will be debugging a separate instance of Visual Studio, so click the ellipsis () button to browse for the Visual Studio IDE. The name of the executable file is devenv.exe, and if you installed to the default location, its path is %programfiles%\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe.
Click OK to close the dialog box.
Right-click the DebugControlLibrary project and select Set as StartUp Project to enable this debugging configuration.
Now you are ready to debug your custom control as it runs in design mode. When you start the debugging session, a new instance of Visual Studio will be created, and you will use it to load the "DebuggingExample" solution. When you open Form1 in the Forms Designer, an instance of your custom control will be created and will start running.
To debug your custom control at design time
Open the DebugControl source file in the Code Editor and place a breakpoint on the Set accessor of the DemoString property.
Press F5 to start the debugging session. Note that a new instance of Visual Studio is created. You can distinguish between the instances in two ways:
The debugging instance has the word Running in its title bar
The debugging instance has the Start button on its Debug toolbar disabled
Your breakpoint is set in the debugging instance.
In the new instance of Visual Studio, open the "DebuggingExample" solution. You can easily find the solution by selecting Recent Projects from the File menu. The "DebuggingExample.sln" solution file will be listed as the most recently used file.
Open Form1 in the Forms Designer and select the DebugControl control.
Change the value of the DemoString property. Note that when you commit the change, the debugging instance of Visual Studio acquires focus and execution stops at your breakpoint. You can single-step through the property accessor just as your would any other code.
When you are finished with your debugging session, you can exit by dismissing the hosted instance of Visual Studio or by clicking the Stop Debugging button in the debugging instance.
Now that you can debug your custom controls at design time, there are many possibilities for expanding your control's interaction with the Visual Studio IDE.
There are several attributes you can apply to your control's properties to manipulate your custom control's interaction with the designer. You can find these attributes in the System.ComponentModel namespace.
You can write a custom designer for your custom control. This gives you complete control over the design experience using the extensible designer infrastructure exposed by Visual Studio. For details, see Walkthrough: Creating a Windows Forms Control That Takes Advantage of Visual Studio Design-Time Features.