Nested user controls and performance implications

[aarf]

Does anyone have an opinion or fact if nested user controls are a best
practice, especially if you want performance from the page?

I've seen pages that nest about 4 levels of user controls.

Thanks

[Peter Bromberg [C# MVP]]

When the page builds the Control tree and needs to make more recursive calls
to complete it's work, that by definition means it takes more time.

There are many other factors involved - the size and complexity of the
controls, whether they use ViewState, etc.
Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com


"aa**@jonathanpadilla.com" wrote:

Does anyone have an opinion or fact if nested user controls are a best
practice, especially if you want performance from the page?

I've seen pages that nest about 4 levels of user controls.

Thanks

[Steve C. Orr [MVP, MCSD]]

I don't think nested controls are normally much of a performance issue,
although there can be some exceptional situations.
I'd say it's usually more about how many controls you have on your page and
how complex and efficient they are. Their relation to each other (nested or
not) is usually of little consequence.

--
I hope this helps,
Steve C. Orr,
MCSD, MVP, CSM, ASPInsider
http://SteveOrr.net

<aa**@jonathanpadilla.comwrote in message
news:11**********************@e3g2000cwe.googlegro ups.com...

Does anyone have an opinion or fact if nested user controls are a best
practice, especially if you want performance from the page?

I've seen pages that nest about 4 levels of user controls.

Thanks