Base pages and abstract functions

[Steve H.]

I use a base page, and decided that an abstract function is best for
guaranteing that the page has been checked for permissions.

basepage (inherits from Page)
-------------------
protected override void oninit(eventargs e)
{
if(!haspermissions())
response.redirect ("/notallowed.aspx")
}

child pages (inherits from basepage)
-------------------
protected override bool haspermissions()
{
return(true)
}

this breaks design mode, are there other ways of doing the same that would
also allow developers to use design mode?

We cant use the builtin formsbased authentication because 3/4 of our current
code is written in asp3.0.

 

[KMA]

Out of interest, why does it break?

 

[Karl Seguin]

The designer creates an instance of all classes, including the base class.
However, since it's abstract it can't. It's just how VS.Net 2003 is,
personally, I'd call it a very buggy behaviour

 

[Karl Seguin]

Don't make the base class abstract...

or

a master page might be able to help
(http://www.metabuilders.com/Tools/MasterPages.aspx free)

Karl

 

[Steve H.]

basepage was abstract also. Was a dumb error.

Now I'm using a virtual function and it works fine. Will probably
response.write a message to the developers that says "you need tro override
has permissions" if it's not already overridden.

Idealy I wanted to make it required to override the function in order to
compile the code.