Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
In my current project, we use lots of user controls. Large user controls (500+ lines code) are breaked up to a few small user controls for easy maintenance.
My question is: most of the user controls are not reusable in other places, but this kind of user control based development complicate the communication between controls, e.g. events are everywhere.
What’s your idea to use User Controls?
Often times I’ll use an ASCX not necessarily so it can be re-used, but to isolate its functionality away from the ASPX. This works great for a navigation menu or a pair of pull-down menus that are used to select city & state for an address form.
The key here is that I don’t want my ASPX to be a mess of micro-behaviors, I want the page to represent a macro behavior.
Now, I know this is all pretty abstract, and I don’t always do it this way, but that’s how I tend to use the technology.