Thinking in components
Yesterday I needed to remove a dropdown list and accompanying webcontrol from a wizard that has been in use for some time.
The dropdown appeared on the .ASPX, it had an accompanying LinkButton which displayed a subform to add a new dropdown item if required. The subform was a separate webcontrol. It struck me as I was removing the various traces of the dropdown and accompanying control that I could have done a better job designing the dropdown and control as a separate piece which could be plugged-in or removed with minimal coding and no impact on the rest of the webform.
The dropdown selection was part of the webform's final processing logic, its appearance was spawned in an earlier method. I don't readily see how this could have been avoided, but I can only consider how a more widget plug-in design where the webform is only conditionally tied to the widget data would benefit overall application design.
It is not often when a field requires removal, but it should be as easy as deleting some lines on a ASPX or ASCX page when it does.