Set the ccTest Project as the Startup Project.
8.6.1. Solution Explorer
In the Solution Explorer, Right Click on the ccTest Project and Select Set as Startup Project.
8.7. Execute Web Form
Run the Web Form from Visual Studio and marvel at your ingenuity.
Click the IDE menu item: Debug=>Start or Click the Play VCR Button to the left of the Solution Configurations DropDownList (usually says Debug or Release)
This is a very simple application that is intended to serve as a testing platform for the Web Control. To test that it is performing properly, simply change the selection of the DropDownList and click the Submit Button. The Label will change to reflect your choice. I leave it as an exercize for the reader to trap the SelectedIndexChanged Event of the DropDownList and modify the Label in that method.
8.8. Browse
Please spend an hour or so, poking around all the code that Microsoft gratuitously generated for you. There is a lot of cruft and if you are intermediate-advanced, you should be able to recognize it as such. Questions to ask yourself, are; Why is it there? Can I leverage the fact that it's there? Should I remove it?
9. Next Steps
Some other things that you may want to do with your Web Control, that you either did not cover or covered minimally are:
Extend Property Grid Support
Specify a Default XML Tag for the Web Control
Specify a TagPrefix
Add Intellisense Support
Package the Web Control for Deployment
More information on many of these topics is included with the MSDN Library. Just open up help in Visual Studio and navigate to the topic: MSDN Library/.NET Development/Visual Studio .NET/Product Documentation/Visual Basic and Visual C#/Programming with Components
If you think tree walking the MSDN Library is painful, searching is just as bad. I highly recommend that you become proficient with Google, or better yet, Copernic.
10. Conclusion
The Design Time environment of Visual Studio .NET is powerful yet mysterious, poorly documented yet accessible, attractive yet aggravating - a true study in contrasts. If you start down the road of extending the Design View further, be prepared for headaches galore, but it will be worth it if you can master it. Very few developers tap into these features and if you resell your components or even work in a large company where other developers will consume your work, you will stand out from the crowd.
I hope that you have enjoyed reading this article and if you have worked through the recipe, I hope your Web Control turned out well. Let me know if there are errors or omissions and I will try to update the Recipe.
11. Resources
F1 and Shift-F1 should be your first line of defense
Copernic Agent Basic (free) is the most powerful search engine I have ever used
Google is the place on the web where you will have the most luck
GotDotNet remains a decent place to visit
CodeProject is a great resource
Microsoft MSDN .NET Framework Home Page Too often, this is a last resort
Download the source
Email the author Will Senn
12. Acknowledgements
Thanks to my Wife for putting up with my 40+ hour focus on writing this.
Thanks to Randy Geyer for assisting me with some of the trickier bits of the IDE.
Kudos to Susan Warren of Microsoft ASP.NET Team fame for her work with Custom Controls.
GotDotNet for the Microsoft ASP.NET QuickStarts Tutorial
If you would like to see your thoughts or experiences with technology published, please consider writing an article for OSNews.
- "VS.Net controls, Page 1/5"
- "VS.Net controls, Page 2/5"
- "VS.Net controls, Page 3/5"
- "VS.Net controls, Page 4/5"
- "VS.Net controls, Page 5/5"



0 