It can be difficult to drill down through an ASPX page to see where your desired object is before you call FindControl. One quick way to figure out the control tree structure is the Document Outline tab of Microsoft Visual Studio. The only caveat is that you will still need to know your Master Page structure.
The complex overkill way is to use Trace="true" under the Page Directive (at the top of the aspx page.) This has other applications as well. For example, instead of debug prints you can see the state of many variables.
Programming Journal C#, Java, SQL and to a lesser extent HTML, CSS, XML, and regex. I made this so other programmers could benefit from my experience.
Subscribe to:
Post Comments (Atom)
Blog Archive
-
▼
2008
(54)
-
▼
February
(13)
- Lazy Load Panel Courtesy of TabContainer and Updat...
- Simple and Complex Drilldown for ASP.Net Objects
- Web User Control Library error
- Prevent RadioButtonList from forcing a line break
- Using Web.config hash for variables using add, key...
- Drilling down a nested master page in ASP.NET to r...
- Intercepting return in list menu items in ASP.NET
- FindContol Solution to add Javascript to a control...
- How to show and hide CalendarExtender and Collapsi...
- Understanding Default Values for User Web Controls
- Creating a ListItemCollection Template User Control
- Installing CA Anti-virus with error on open
- Web Control IDs INamingContainer to avoid duplicat...
-
▼
February
(13)
No comments:
Post a Comment