Abstract Base Page in .Net 2.0

[ayende]

I want to have a page that contains some UI & logic, and have a set of
pages that inherit from it, and provides minimal additional items.

The best scenario is that teach child page need to give the parent page
a drop down list with items and a couple of strings to match.

I would like to be able to use markup to do it, since it's a lot easier
this way, and there is really no behavior about the child pages.

Any ideas?

 

[Dimitrios Toulakis]

take a look at master pages

Dimi

 

[ayende]

I did, but it's not really helpful, since I need to put _logic_ in the
base page, and only get very little different information from the
child page.
There isn't really a way to force a child page to implement a spesific
interface, like I can do with abstract base page.

 

[Kevin Spencer]

Use a Master Page.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
If you push something hard enough,
it will fall over.
- Fudd's First Law of Opposition

 

[Mikeon]

I've had the same problem. I thought that if I add protected field to
the base page and name it i.e.: DropDown1, and then in child pages add
a control on a form with the same ID, then it would be accessible in
the base page (it would not be null). It came out that it is not the
case. It was allways null.
I is possible that it was null because the child pages were using
master page, but I had no time to test it, so what I have done is
declared an abstract property DropDown1 in the base class and every
page that inherits from it, must override it by returning the concrete
instance of the DropDownList control.
In the base page I'm using this property.

If anyone has tested the approach I've described that hasn't worked for
me, please comment on this.

 

[Patrice]

Possible solutions not knowing what exactly you are after :

#1. Still double check master pages. You can have logic in master pages and
you can expose whatever you want to child pages. Have you tried ?

#2. Else you can also have a page that inherits from a base page. It should
cause no problem (you can even define this as a default in the web.config
file). Have you tried ?

#3. Finally some people are using user controls loaded into a "main" page.

Which point exactly causes a problem ? IMO the first step will likely to
double check your requirements before choosing the appropriate solution...

 

[Scott Allen]

I did, but it's not really helpful, since I need to put _logic_ in the
base page, and only get very little different information from the
child page.
There isn't really a way to force a child page to implement a spesific
interface, like I can do with abstract base page.

I'm not following you here - you can put logic in a MasterPage.