As long as you have the controls stacked, it is quite easy to run routines
from one control to the next. If you are going back through the parent, you
should rethink your architecture, as you are creating a nightmare.
In general, I put the working code into libraries. In some cases, there is a
UI library (a facade, if you will) that puts things together and allows for
inversion of control without stacking up code in the actual ASPX pages
and/or controls. I put the hard working bits in the business layer (and some
moving bits in the data layer), feeding the actual repository classes so I
can easily create simple mocks. Very testable and it makes it easy to swap
out user interfaces. Following this method, there is no need to call from
control to control, as the actual work is in classes in the libraries used
by the site.
--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA
Blog:
http://feeds.feedburner.com/GregoryBeamer
********************************************
| Think outside the box! |
********************************************