>Whoa! I think your over-complicating things. Just try my suggestion to map your framework oResponse/oRequest properties to Current.Response/Current.Request - that should be all you need to do (apart from, as you say, removing some dead wood from the current global.asax)

The problem I would have with that approach is that it wouldn't resolve all the other issues of all the rest of the properties which can be updated by another instance and completely mix up the current instance. I understand the current context would resolve the issue of oResponse and oRequest. But, I have about 200 properties and those can be updated by any other instance so I would still have a problem there.

>That's not a copy - it's just another reference to the same object...

From this point, loApp properties shouldn't be affected by LXFramework, isn't it? If I declare an instance of the current state of LXFramework at this point, if another instance updates LXFramework.cCookie for example, this should not affect loApp. Or, did I declare it wrongly for such need?