I'm tearing my hair out here!
I have a composite server control 'FilterList' which has a collection of child controls 'FilterField' which are themselves composite controls. they're declared like this:
<cc1:FilteredList ....>
<cc1:FilterFieldSection...
<cc1:FilterField ...
<cc1:FilterField ...
</cc1:FilterFieldSection>
</cc1:FilteredList>
Now, what's confusing me is that the CreateChildControls method of the FilterField controls is being called before the CreateChildControl of the FilteredList. And also, the this.Page is always null at this point. Why would that happen? It's meaning that none of my filterField controls are holding their data via the ViewState.
Please help before I'm completely bald.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Hi, thanks for the response,
Yeh I know about the page lifecycle but my problem is that the child controls are being created before their parent control. I want them to be created by the parent control in the CreateChildControls() method but they're not being. It seems the page is creating them so they end up with no parent (this.Parent is null) and no page (this.Page is null) and the viewstate doesn't work at all.
Without some of your code it's difficult for me to see what is going on. It could be as simple as forgetting to override the CreateChildControls method.
The child controls have to be added to their parent control before any child control properties are set and where this is done in the page lifecycle makes a huge difference.
This may help: http://aspalliance.com/359
Thanks for your help. Having found the problem now, I can appreciate that you would have needed much more code to figure it out.
The problem was that the child controls had a property on them which called 'EnsureChildControls'. I was referencing this property too early in the page life cycle and therefore causing the CreateChildControls method to execute before it should have.
Business Accounts
Answer for Membership
by: kev-doggPosted on 2007-08-07 at 11:03:40ID: 19648227
The OnInit method is the first method that is called in the page lifecycle. LoadViewState is the third method so your viewstate data is not available when the child controls are initialized. The control is stable in the Load event where it has been initialized and the state has been reconstructed.