I am buffing up on ASP.NET Server Controls and a central dilemma seems to be whether to inherit from System.Web.UI.Control or System.Web.UI.WebControls.WebControl. It really seems to boil down to whether you will be presenting visual elements or not. If you are presenting visual elements in your control, you should probably inherit from WebControl. Why? Inheriting from System.Web.UI.Control basically gives you all that you need from the ASP.NET page framework but WebControl gives you the added control of applying styles to your controls as well as Attributes. A couple of these are AddAttributesToRender, ApplyStyle, CopyBaseAttributes, CreateControlStyle, and MergeStyle; none of which are available in Control. Using these methods with the base types and enums from Control (WebControl inherits Control and IAttributeAccessor) you have a very powerful mechanism for developing a Server Control AND a readily available mechanism for making your controls visually pleasing.
Server Control Development Tip #1: Determining Whether to Inherit from Control or WebControl in a Server Control
New on Geeks with Blogs
- Your Customers Build the Features Now
I let a tool I liked sit dead for a year rather than build the features I wanted. An MCP server meant I never had to, and your customers can do the same to your product.
- Get the Size of a Directory in Linux the Easy Way
du -sh for the quick answer, ncdu for the cleanup, df for the disk itself: every command for checking directory size in Linux, plus why du and df never agree.
- Vim Search and Replace: The Ultimate Guide
One :%s command replaces every match in a file before a find dialog would even open. The Vim substitute patterns worth the muscle memory: flags, ranges, capture groups, and multi-file edits.
- Because of AI, You Need a New Development Team
Your existing team is buried in the complexity of your existing product. AI rewards the team with a blank slate. Most companies don't have one.