Using .NET extender controls can help you avoid tedious subclassing of existing controls. But what are extender controls and how do you use them? Find out how these "non-visual" controls can be a great design-time short cut for people who want to spend less time writing code.
by Jonathan Lurie and Timothy Stockstill
July 14, 2004
n our previous article "Put a 24-hour Lockdown on Your .NET UIs," we discussed various ways to augment user interfaces to interpose underlying business logic and data engine security constraints. We recommended the use of extender controls. The purpose behind this suggestion was clear: We don't like to code. In fact, if given a choice between coding and surfing, only one question remainswhere's the wax? While it is certainly possible and in some cases necessary to subclass existing controls, we prefer to reserve such methods for situations just shy of thermonuclear destruction.
However, one thing we did not expect when we made our suggestion was that some of our readers would be unfamiliar with the details of extender controls, their creation, and their operation. While such a discussion was outside the scope and coverage of the original article, we decided that it would make a fine subject for whole new article. So without further gilding the lily and with no more ado, we present to you our champion, the Knight of the Lazy Programmer, the Extender Control.
It's quick, easy and you get access to all the articles on DevX.
This registration/login is to allow you to read articles on devx.com. Already a member?
To become a member of DevX.com create your Member Profile by completing the form below. Membership is free!