Hi,

>>But I wonder whether you would be better off subclassing the page class for use with the framework and passing the page to the framework somewhere during the page creation. That way only valid pages (in fact only pages deliberately subclassed) would be passed to the framework. (Sorry, I'm a bit rusty on this and have my head in a VFP bucket at the moment so I may be missing something (or a lot<s>)
>
>I think this is probably the approach that would resolve a few of my issues right now. First, I need to assure that only aspx page goes in the framework. Secondly, I have the issue of the redirect which I need to assure that oPage would also be initialized.
>
>Rick, earlier on, mentioned about the factory approach. I think I will really have to build a DLL for the factory and handle it at that level. By that, I would be able to remove the PreRequestHandlerExecute() event from my global.asax. This would also provide me more flexibility. I would then be able to add this DLL reference in the httpHandlers from the Web.Config file. So, only aspx page would go in the framework and this would also work on a redirect to get a handle of the page.

I saw that Rick had also suggested your own HTTPHandler and I'm sure a handler factory is the ideal way to go - but you could just check the handler type and only pass the request to your framework if it's an ASPX page (or other type of interest).

Regards,
Viv