new Page class

[m.farlocchio]

Hi all,
I was discussing with some colleguees about developing a new Page
class.
Some says that it's impossible defining a new Page class without
hineriting
System.Web.UI.Page
Others says that it's possible to develop a new Page class that doesn't

hinerits System.Web.UI.Page.
I think it's possible,but I'm not able to demonstrate... any help?

Thank you in advance!
Regards

Marco

 

[Kevin Spencer]

It is possible to develop a class that does not inherit System.Web.UI.Page,
and that serves the same purpose as System.Web.UI.Page, yes.

Help? Well, the following link is to the freely-downloadable Microsoft .Net
1.1 SDK. It has everything you need to know in it.

http://www.microsoft.com/downloads/...A6-3647-4070-9F41-A333C6B9181D&displaylang=en

I can give you a few suggestions as to where to start in your study, with
regards to this particular topic. First, you will need to study the
structure and inheritance hierarchy from which System.Web.UI.Page was
derived. At its root, it is a System.Web.UI.Control. This means that it has
everything in it that every System.Web.UI.Control has. It immediately
inherits System.Web.UI.TemplateControl. This provides the templating
functionality which it has, just like a System.Web.UI.UserControl. It
implements IHttpHandler, which is what provides its capability of handling
and responding to HTTP requests from a client. Because IHttpHandler relies
on .Net configuration files, you will also want to study up on configuration
files.

Once you understand all of the above, you will be able to write your own
"equivalent" of a System.Web.UI.Page class. Of course, if you just want to
win an argument with a "colleague," it may not be worth the trouble. Some
people will go to great lengths to win an argument, however, Perhaps you are
one of them.

--
HTH,

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

 

[m.farlocchio]

Thank you Kevin!
Now I wanna myPageClass!!
Now I'm trying to understand all structure and inheritance hierarchy of
Page Class.
I'm looking to SDK documentation, but I'm finding it not very helpful
for my objective!
Any suggestion, please!

But i'm thinking it will be very hard... and maybe not productive?
If I will develop a new page Class and all my new application will
implement it,
what will happen when there will be a new NET framework upgrade?

Thanks
Marco